Add garmin-grafana LXC script

[aliaksei135]

✍️ Description

Adds a new LXC container script for garmin-grafana. This is an application to locally display fitness metrics from Garmin Connect using InfluxDB and Grafana.

🔗 Related PR / Issue

Link: N/A

✅ Prerequisites (X in brackets)

• Self-review completed – Code follows project standards.
• Tested thoroughly – Changes work as expected.
• No breaking changes – Existing functionality remains intact.
• No security risks – No hardcoded secrets, unnecessary privilege escalations, or permission issues.

---

🛠️ Type of Change (X in brackets)

• 🐞 Bug fix – Resolves an issue without breaking functionality.
• ✨ New feature – Adds new, non-breaking functionality.
• 💥 Breaking change – Alters existing functionality in a way that may require updates.
• 🆕 New script – A fully functional and tested script or script set.
• 🌍 Website update – Changes to website-related JSON files or metadata.
• 🔧 Refactoring / Code Cleanup – Improves readability or maintainability without changing functionality.
• 📝 Documentation update – Changes to README, AppName.md, CONTRIBUTING.md, or other docs.

---

🔍 Code & Security Review (X in brackets)

• Follows Code_Audit.md & CONTRIBUTING.md guidelines
• Uses correct script structure (AppName.sh, AppName-install.sh, AppName.json)
• No hardcoded credentials

[CrazyWolf13]

Wow, thanks a lot for this script!
This seems like an awesome thing, I wanted to search something like this too.

this looks already pretty good, could you take a look at the marked things?

[CrazyWolf13]

Suggested change

# shellcheck disable=SC2016

[aliaksei135]

The following line needs to replace the string literal ${DS_GARMIN_STATS}, so any parameter expansion should be prevented, therefore I have kept it in single quotes. This causes a warning from the linter though. I think it should be kept in to prevent future edits from accidentally causing parameter expansions here.

See this line in the source repo.

It's not the way I would have done it, but here we are :)

[tremor021]

Linter check exclusions are kept in the vscode config, like so

"shellcheck.exclude": [
        "2164",
        "1090",
        "1091"
    ],

[aliaksei135]

Wouldn't this exclude the check across the entire repo? It would still be useful in other scripts, just not in this edge case