Marking a milestone by bumping the version to v2.1.0, the milestone being commits and releases are now signed with PGP keys.
As per normal, below follows some changes and updates.

Bug fixes

• #67 Encryption issues with NVME (to quick to encrypt) has now been fixed. The solution was (at least for now) to add a 25 millisecond delay to the .add_partition() function, where it will keep delaying until the partitions of the device changes from the original state. There's a slight risk here that this might have some weird edge cases where the disk had identical partition setup before the formatting. So there's a grace period of 10 seconds. But the long term solution would be to check the partition list after wiping it - and then do the check.
• genfstab was incorrectly called since piping doesn't work seamlessly in Popen() and has been done so for a while. It hasn't caused any alarming concerns, but it was best to update according to the installation manual. Especially since supporting custom mounts etc becomes more convenient and supported in the installer.
• Fixed an issue with sys_command where some but not all commands would get their output garbage collected by the .strip(). To my knowledge, there's very few commands that has had any issues, and in those cases they have been remedied in another way - which is perhaps a bit lazy. So sys_command is now fixed (but should be looked over further).

New features

• Added a archinstall.harddrive([size], [model], fuzzy=False) which can be used to select/find harddrives based on their model or size, fuzzy allows to be slightly off on the model or size (be careful when using fuzzy if disks are nearly identical in size).
  (This change also required BlockDevice() to contain the model name in the internal .json() helper function)
• installation instance (the current installation being performed) now contains a .mount(partition, relative-mountpoint) that can mount a partition "inside the installation" *(by prepending the installation mountpoint, usually /mnt automatically). This simply makes mounting partitions for/to the installation a bit more intuitive, as it's implied that it's for the installation - which was set up with a root mount point to begin with. It just ensures that we don't accidentally mount anything outside the installation when it in fact was meant for inside the installation.