Fix PATH value in /etc/environment

[DevCas1]

Fixes environment's PATH being empty, thus being useless when SSH-ing into machines

Description

When manually SSH-ing into my Archcraft machine, it connects with a session. However, using Visual Studio Code's Remote-SSH, it initially SSH-es into the machine headless. With /etc/environment's PATH not pointing to the system binaries, it could do nothing and would fail. Adding paths to system binaries restores headless SSH functionality.

Fixes #455

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)

User Impact

Fixes headless SSH sessions into Archcraft machines.

Performance Impact

None

How Has This Been Tested?

I have tested this on my local machine running the latest version of Archcraft.
I could not use Visual Studio Code's Remote-SSH because it uses headless SSH to set up the remote server, which would fail because it could not find expected system binaries. Using this PATH value fixes this issue completely. I have confirmed this also fixed the same issue on a friend's machine running a clean install of Archcraft.

Software Configuration:

• Operating System: Archcraft
• Software version: 7.1.2-arch3-1
• System Specs: AMD Ryzen 7 Microsoft Surface (R) Edition (16 x 1976)
• Graphics Card: Radeon Graphics based on RDNA 3 with 12 compute units (768 stream processors)

Checklist:

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
  • Not applicable
• I have made corresponding changes to the documentation
  • Not applicable
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes