Hide looback devices from graphical interfaces

[jumpyvi]

Sysexts, overlay, verity, homed and a bunch of theses systemd tool add an absurd amount of looback devices.

Should be add a udev rule to hide them? If you click on one currently from Files, you will just get some random error.

If not a udev rule, it should maybe be moved to io.elementary.files as a setting (on by default).

This is a VM I've barely used, using sysext-utils, custom sysexts, drivers or homed; would result in having even more loopback devices:

Before

After

We might even want to hide all the default sysupdate partitions, you can't do anything with them in a graphical interface, just keep "File System"

[github-actions]

Installer builds for d61756e

Do not use these installers for production systems. They are intended for testing purposes only. They will update to the latest PR build, which will break your install eventually.

Arch	ISO	Checksum
amd64	elementaryos-9.0-proposed-x86-64.20260926221836.iso	sha256
arm64	elementaryos-9.0-proposed-arm64.20260926221742.iso	sha256

[vjr]

This diff looks good (the current idea of it) because it's hiding loopbacks closer to the core/source using udev, instead of asking others (like the stock or third-party file managers, terminals etc) to handle it?

What if a user really wants to list/show all loopbacks? Will they reveal themselves if they do sudo fdisk -l in a terminal? Or maybe run the Files app as administrator? If so, this PR seems good to me.