rebase fedora-mate to 39

[thelamer]

Rebases to fedora 39, not many changes and low impact 6 month update. Adds caja as the missing file manager was messing with init. The new startup messages from X can be ignored those are just warnings and will be expected in head versions of X from here out.

[LinuxServer-CI]

I am a bot, here are the test results for this PR: https://ci-tests.linuxserver.io/lspipepr/webtop/fedora-mate-e0042c0f-pkg-e0042c0f-dev-1641c6f9db855eec23e7a7f54b11e768abf94895-pr-188/index.html https://ci-tests.linuxserver.io/lspipepr/webtop/fedora-mate-e0042c0f-pkg-e0042c0f-dev-1641c6f9db855eec23e7a7f54b11e768abf94895-pr-188/shellcheck-result.xml	Tag	Passed
amd64-fedora-mate-e0042c0f-pkg-e0042c0f-dev-1641c6f9db855eec23e7a7f54b11e768abf94895-pr-188	✅
arm64v8-fedora-mate-e0042c0f-pkg-e0042c0f-dev-1641c6f9db855eec23e7a7f54b11e768abf94895-pr-188	❌

[thespad]

arm64 CI failed, but could be a qemu thing.

[thelamer]

arm64 CI failed, but could be a qemu thing.

I have manually tested arm images(local built not pulls) on an ampere OCI instance. Yeah they are all qemu.

[thelamer]

Startup logs for reference and merging:

[migrations] started
[migrations] no migrations found
usermod: no changes
───────────────────────────────────────
  _____ __ __ _____ _____ _____ _____ 
 |     |  |  |   __|_   _|     |     |
 |   --|  |  |__   | | | |  |  | | | |
 |_____|_____|_____| |_| |_____|_|_|_|
       _____ __ __ _ __    ____  
      | __  |  |  | |  |  |    \ 
      | __ -|  |  | |  |__|  |  |
      |_____|_____|_|_____|____/ 

  Based on images from linuxserver.io
───────────────────────────────────────

To support LSIO projects visit:
https://www.linuxserver.io/donate/

───────────────────────────────────────
GID/UID
───────────────────────────────────────

User UID:    911
User GID:    911
───────────────────────────────────────

...........+++++++++++++++++++++++++++++++++++++++*....+.........+.+.........+...+++++++++++++++++++++++++++++++++++++++*....+...+...........+.+..............+......+..........+.....+....+......+........+....+...+.........+...+..+....+.....+.+.........+......+...+..+....+.....+......+...+.+.....+.+......+..+......+......+.+...+...........+......+....+.....+................+..+...+...+.+..............+.+......+.....+.........+...+...+...+.+.....+....+..+.........+......+.......+.....+.......+...+......+..+...+......+...+.....................+......+...+......+...............+....+..+.+.........+...+.....+..........+............+.........+.....+.+......+...+.........+...+...............+...+...............++++++
...+.+...+...+.....+...+...............+.......+..+++++++++++++++++++++++++++++++++++++++*....+......+............+.+......+.....+.+..............+.+.....+++++++++++++++++++++++++++++++++++++++*.+......+...+...+..+.......+.....+.+........+.........+.+..+............+.+............+.........+.....+.+..+............+...+...............+..........+...+.....+.........+......+.......+......+.....+.+.....................++++++
-----
[custom-init] No custom files found, skipping...
_XSERVTransmkdir: ERROR: euid != 0,directory /tmp/.X11-unix will not be created.

Xvnc KasmVNC 1.2.0 - built Nov  7 2023 19:29:26
Copyright (C) 1999-2018 KasmVNC Team and many others (see README.me)
See http://kasmweb.com for information on KasmVNC.
Underlying X server release 12014000, The X.Org Foundation

[ls.io-init] done.
[root@f565de4f8a70 /]# The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Could not resolve keysym XF86CameraAccessEnable
> Warning:          Could not resolve keysym XF86CameraAccessDisable
> Warning:          Could not resolve keysym XF86CameraAccessToggle
> Warning:          Could not resolve keysym XF86NextElement
> Warning:          Could not resolve keysym XF86PreviousElement
> Warning:          Could not resolve keysym XF86AutopilotEngageToggle
> Warning:          Could not resolve keysym XF86MarkWaypoint
> Warning:          Could not resolve keysym XF86Sos
> Warning:          Could not resolve keysym XF86NavChart
> Warning:          Could not resolve keysym XF86FishingChart
> Warning:          Could not resolve keysym XF86SingleRangeRadar
> Warning:          Could not resolve keysym XF86DualRangeRadar
> Warning:          Could not resolve keysym XF86RadarOverlay
> Warning:          Could not resolve keysym XF86TraditionalSonar
> Warning:          Could not resolve keysym XF86ClearvuSonar
> Warning:          Could not resolve keysym XF86SidevuSonar
> Warning:          Could not resolve keysym XF86NavInfo
Errors from xkbcomp are not fatal to the X server