The efibootmgr utility displays the EFI's own boot menu options. These options point to various things -- built-in tools like an EFI shell or the setup utility; boot features for devices like network cards; the default/fallback boot loader for a disk; or individual boot programs on the EFI System Partition (ESP). It's this last category that's relevant to your question, but your efibootmgr output shows entries from most or all of the categories.
Most OSes install an EFI boot loader on the ESP, with the approved location being subdirectories of the EFI directory. In the case of Ubuntu, this location is EFI/ubuntu. Ubuntu mounts the ESP at /boot/efi, so in Ubuntu, the boot loader is stored at /boot/efi/EFI/ubuntu. Importantly, every instance of Ubuntu will install its boot loader to this same location and create an identical EFI boot manager entry, or re-use an existing one. Ubuntu uses GRUB 2 as the boot loader by default. Thus, if you've installed Ubuntu 20.04 and 22.10, as you specified, then they'll end up trashing each others' GRUB 2 binaries and configuration files. Whichever one was installed or updated its GRUB 2 more recently will take over that one boot entry.
This shouldn't normally be too big of a problem if you've got just two Ubuntus installed, since they'll detect each others' configurations, and your GRUB 2 menu will show both options. This can become more of a problem when other distributions get added to the mix. Your output shows a debian entry, for instance. If you set up both the Ubuntus, then install Debian, then Debian's GRUB 2 will become the default. It might or might not do a good job of detecting the Ubuntu installations and booting to them. When one of the Ubuntus gets updated, it might become the default boot program.
Using the firmware's boot manager to select between these options is also possible, but as I said, some options will end up being "folded" together into a monolithic entry. In theory, you could disentangle this by giving each Ubuntu its own GRUB 2 on the ESP -- say, EFI/ubuntu2004 and EFI/ubuntu2210. I don't happen to know offhand what GRUB configuration files you'd have to modify to make this happen, though.
Another option is to bypass GRUB 2. Both systemd-boot and rEFInd are designed to help with more complex multi-boot configurations compared to GRUB 2, which really isn't well suited to this task. (Disclaimer: I'm the maintainer of rEFInd, so I'm not exactly unbiased.) Of the two, systemd-boot is simpler in design but more difficult to set up, especially since it requires kernels to be stored on the EFI System Partition (ESP). (At least, that was the case the last I checked.) rEFInd, OTOH, can read kernels from several Linux filesystems (namely ext2/3/4fs, Btrfs, and ReiserFS), and it requires minimal configuration changes on the OSes it's intended to boot. You can get separate entries for each of your Ubuntu or Ubuntu-like OSes with either program. Assuming Secure Boot is disabled, you can try rEFInd without installing it by using its USB flash drive version; however, if you use separate /boot partitions (like with an LVM setup), you'll need to adjust boot options by hitting Tab or F2 twice, rather than Enter, to launch the OS.
