Installer: Handle AppArmor profile installation automatically

[qwertychouskie]

Currently, the user is required to manually run these commands to install the AppArmor profiles necessary for many of the WPILib applications to work:

sudo cp ~/wpilib/YEAR/frccode/AppArmor/* /etc/apparmor.d/
sudo systemctl reload apparmor.service

The installer should probably handle this by default, as doing 95% of the installation manually but requiring the user to do the remaining 5% is extremely likely to result in the user missing the step and wondering why applications just silently don't launch. (This was my situation just minutes ago, hence me opening this issue.)

It is also possible to programmatically set the launcher on the desktop to allow launching, see https://askubuntu.com/a/1391903:

gio set "~/Desktop/FRC VS Code 2025.desktop" metadata::trusted true
chmod +x "~/Desktop/FRC VS Code 2025.desktop"

[calcmogul]

We should check /etc/lsb-release to confirm it's Ubuntu first since not all Linux OSes have AppArmor installed. Also, we'll need an elevation prompt to be able to run those commands as root.

[qwertychouskie]

We should check /etc/lsb-release to confirm it's Ubuntu first since not all Linux OSes have AppArmor installed.

The most proper way would probably be to check if apparmor.service is present/running, but on the other hand, it's probably fine to just always install the files, they shouldn't hurt anything if AppArmor isn't being used, outside of eating a couple extra KB of disk space.

Also, we'll need an elevation prompt to be able to run those commands as root.

Just use pkexec instead of sudo, it'll handle the GUI part.

[calcmogul]

it's probably fine to just always install the files, they shouldn't hurt anything if AppArmor isn't being used

I strongly disagree with this. It's bad enough to have random files installed as root into a system folder on OSes that don't need them. It's even worse that those system files won't be tracked by the system package manager. If those files are force-installed, I would just avoid running the installer on my Arch Linux machine alltogether.

[qwertychouskie]

it's probably fine to just always install the files, they shouldn't hurt anything if AppArmor isn't being used

I strongly disagree with this. It's bad enough to have random files installed as root into a system folder on OSes that don't need them. It's even worse that those system files won't be tracked by the system package manager. If those files are force-installed, I would just avoid running the installer on my Arch Linux machine alltogether.

Just checking if /etc/apparmor.d/ exists is probably the simplist way to handle this.