They are only needed when building the akmods, but not when shipping them.
This should considerably remove the bloat from the images without affecting the existing functionality.
* chore(gnome-extensions): Make extension URL quering more robust
If there are multiple Gnome extensions with the same name, & they are compatible with Gnome version in the base image, then build will fail.
Previously, build would always fail if there are extensions with duplicate names.
* docs(gnome-extensions): Fix typo
* docs(gnome-extensions): Mention github repo
* fix(gnome-extensions): Version checking
* chore(gnome-extensions): Make operation order better for reading
* feat(gnome-extensions): Use new PK ID installation method
* fix(gnome-extensions): Unbound variable error
* fix(gnome-extensions): Legacy config order logic
* docs(gnome-extensions): Fix spacing
* docs(gnome-extension): Delete false-claim about better config readability
* chore(gnome-extensions): Add safe check for "null" in if `jq` parsing
* chore(gnome-extensions): Update uninstall step to use PK
This will break config for uninstalling extensions in literal names, but I bet that no one uses this feature yet since this extension is still new & fresh, so I'll just break it.
* Revert to the current module state
* docs(gnome-extensions): Add README details about missing gschema.compiled file
* chore(gnome-extensions): Introduce hybrid literal-name/PK config
If 2 or more same-named extensions are recommended, then user is recommended to use PK ID instead.
* chore(gnome-extensions): Ignore ShellCheck 2128 error, since it's harmless & intended
* chore(gnome-extensions): Also ignore harmless SC2178 notice
* chore(gnome-extensions): Use UUID for matching compiled.gschema workaround rather than extension name
* docs(gnome-extensions): Add note in module.yml that PK can be used
