Added shared memory multi-server feature

[jkuro-tii]

Description of changes

The memsocket application has been enhanced with the following new features and updates:

Host Support:
    The application can now run on the host in addition to virtual machines (VMs).

Multi-Server Capability:
    Multiple memsocket instances operating in server mode are now supported.
    Each server instance is configured with a list of specific client IDs it serves.
    Multiple servers can run simultaneously on a single VM or the host.

Client ID Exclusivity:
    Each client ID must be managed by only one server across the entire system.

Configuration Updates:
    Renamed some Nix configuration options for clarity.

Option Changes:
    The -c and -s options have been swapped:
        -c: Now used for running in server mode.
        -s: Now used for running in client mode.
    A new -l option has been introduced for server mode to specify the list of client IDs to be serviced.   
    A new -h option has been introduced for indicating run on the host

Documentation: https://confluence.tii.ae/x/uEPOAg

Checklist for things done

• [ X] Summary of the proposed changes in the PR description
• [ X] More detailed description in the commit message(s)
• [ X] Commits are squashed into relevant entities - avoid a lot of minimal dev time commits in the PR
• Contribution guidelines followed
• Ghaf documentation updated with the commit - https://tiiuae.github.io/ghaf/
• PR linked to architecture documentation and requirement(s) (ticket id)
• Test procedure described (or includes tests). Select one or more:
  • Tested on Lenovo X1 x86_64
  • Tested on Jetson Orin NX or AGX aarch64
  • Tested on Polarfire riscv64
• Author has run make-checks and it passes
• All automatic Github Action checks pass - see actions
• Author has added reviewers and removed PR draft status
• Change requires full re-installation
• Change can be updated with nixos-rebuild ... switch

Instructions for Testing

• List all targets that this applies to:
• Is this a new feature
  • List the test steps to verify:
• If it is an improvement how does it impact existing functionality?

[josa41]

Nothing too obvious to comment in the code.
I did test this also with pulseaudio and got everything to work just fine.
During my testing i found two issues.

1. If the application socket (pulseaudio in my tests) is not available when memsocket starts then data does not reach the socket. Restarting memsocket helps for this or adding a delay for memsocket to start after the application.
2. Memsocket/kernel crashes when a second memsocket server is started from command line on the same VM with another id

I passed more details to Jarek in slack

[mbssrc]

Any idea how this can or should be tested?