[GhafPkgs] Update Audio Control

[baz2142]

Add AppVM names support. Now you can see, which stream belongs to which AppVM

Description of changes

Checklist for things done

• Summary of the proposed changes in the PR description
• More detailed description in the commit message(s)
• 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

Run Audio Control
Run Chromium and check, that steams appear under "Chromium-appvm" name
Another audio apps, if it is possible

[leivos-unikie]

Tested on Lenovo-X1 (rebuild switch)

• ci-test-automation pass
• all menu icons work
• audio control tool shows streams by vm name but there is strange note "No streams from the AppVM" although I am listening sound from that particular app-vm

[leivos-unikie]

Also noticed now that the audio streams stay open although corresponding apps are closed. Is this ok?

[baz2142]

Also noticed now that the audio streams stay open although corresponding apps are closed. Is this ok?

I think, now every AppVM has it's own stream for the all apps. So it's not like every application inside an AppVM creates a stream, but every application inside it goes through the same stream

Is it correct, @josa41?

[josa41]

Also noticed now that the audio streams stay open although corresponding apps are closed. Is this ok?

I think, now every AppVM has it's own stream for the all apps. So it's not like every application inside an AppVM creates a stream, but every application inside it goes through the same stream

Is it correct, @josa41?

Yes in current version the app-vm created the pulseaudio tcp tunnel open even though the app is closed. The actual pulseaudio application audio stream is closed but tcp tunnel that carries the stream stays open.
From audio-vm
pactl list sink-inputs or pactl list source-outputs should show the actual application audio streams

I have made a patch that would fix the tcp stream so that the connection will get closed along with the app: #852