* fix: Matugen relative paths
The Problem
All matugen config files (matugen/configs/*.toml) used relative paths like:
input_path = './matugen/templates/gtk-colors.css'
However, matugen was interpreting the relative paths ./matugen/templates/ as relative to its current execution context (which could be /tmp or another directory), not relative to $SHELL_DIR. This caused the "template doesn't exist" warnings and the "Failed to get input and output paths from hashmap" errors.
The Fix
Modified scripts/matugen-worker.sh to replace all relative template paths with absolute paths before passing them to matugen:
`sed "s|input_path = '\./matugen/templates/|input_path = '$SHELL_DIR/matugen/templates/|g"`
* matugen: leave user-templates as-is
---------
Co-authored-by: bbedward <bbedward@gmail.com>
* Allow user's matugen config to be ran by dms
matugen-workers.sh now also loads the configs and templates from `~/.config/matugen/dms` and handles them the same way dms does its own matugen configs.
* Do not auto create user's matugen directories
- Add surface shift option, start from surface by default (previously
was surfaceContainer). Old colors can be attained by changing it back
to "container" in theme colors
- Remove borders on surface elements, mostly
- Fix popup distances
- Use surfaceContainer/sch by default on widgets
