lsblk gets you information about block devices (disks and partitions). Take a look at an fstab entry:
UUID=a6c3b56a-3d2b-4cec-9f20-deab5af162bd / btrfs subvol=root,compress=zstd:1 0 0
The first column here is the device identifier, which is a UUID in this case.
Then the mount point, which is / and is the path that this filesystem will be mounted at
btrfs is the file system type
Then there are some mount options
The two numbers at the end are used by the dump and fsck commands. You can check out man fstab to read more about all this. (but you can also just use zero for both)
So, when you run `lsblk -o PATH,FSTYPE,UUID` it will show you the filesystem type and UUID for each block device. Since your new drive is /dev/nvme1n1p1, which is a PATH, you’ll find that line and then use the FSTYPE and UUID in your /etc/fstab
From there what do I do to get it to auto-mount without needing admin perms each time?
This is really Linux 101… Whatever mount thing that is asking you for a password is totally nonstandard and weird (probably an alternate systemd mount unit or something). But! the mounting will occur with elevated permissions. Filesystems that are in fstab are mounted as root without your intervention, though, so you still won’t enter a password at boot.
Normally, to make something mount at boot, you add it to /etc/fstab and that’s it. That is the file that is used to mount filesystems at boot. And it is what the Fedora installer (anaconda) did. As your generated file says, you should also run systemctl daemon-reload (probably as root) after editing the file in this case.
Also, I know Fedora and Ubuntu and even the Arch wrapper distros act like you don’t need to know anything to use Linux on the desktop, but it really is much better to know the basics! Every basic Linux book from O’Reilly is good and so is Linux for Dummies (my introduction to the topic way back in the 20th century)