When an Array or Choice that contains Spa:Id appears as a value for an object
field, it is possible to retrieve the Id type from that object field type.

For consistency with LUA

and fix some coding style issues

* the type checks were wrong, it was requiring the key to be string
  and the value integer
* add the ability to use "any" or "all" for a key, saving us the trouble
  of passing -1 from lua (int64) into a uint32 (ugh!)
* use a GArray instead of manual malloc/realloc
* allocate the array as late as possible, to minimize the risk of leaking
  its memory if we hit luaL_error()

* skip the shebang before loading the file in the interpreter,
  as # is not a valid lua comment
* allow loading scripts with a relative path in interactive mode

filename: foo.lua -> category: script/foo

NULL crashes the journald writer

Ensure that no part of the description string is empty, otherwise fall back
Fix logic with dev and/or subdev being 0

https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/6079830591bc34433e4ba8e6142061e59022dfe2

https://gitlab.freedesktop.org/pipewire/pipewire/-/commit/aea79cd79ca0f08fe6aae566d23bbf972e27092f

The advantage is that luaL_tolstring behaves the same as the native lua
tostring() function, while lua_tostring() does not. In particular, boolean
values are converted properly to "true" and "false" now, while they were
not converted with lua_tostring()

Add a unit test too

This file is meant to provide the equivalent of pipewire-media-session's
'with-pulseaudio' flag file

This allows altering monitor properties or adding rules in different
lua files that get loaded before 90-enable*.lua

and also make the default of alsa.reserve to be false, for easier scripting

pipewire/pipewire!456

When we convert from a lua table to a GVariant dictionary, it is not
possible to maintain the hybrid string & integer keys approach that Lua
has for tables, so we convert all keys to strings and a table becomes a{sv}

When we convert back from a{sv} to a table, it is desirable to get back
the integer keys wherever possible.

The use case is to pass "arrays" (i.e. tables with integer keys) from
the configuration files to the lua scripts, without losing the properties
of the "array"

* index array items from 1
* handle any kind of value, not just GVariant basic types
* unit test

* Add more generic lua -> gvariant conversion
* Cleanup the gvariant -> lua function and rename it

G_VARIANT_TYPE_DICTIONARY also catches the VARDICT case