WIP feat(sabnzbd) adding exportarr for metrics

[ac1dburnz]

Description

⚒️ Fixes #

⚙️ Type of change

• ⚙️ Feature/App addition
• 🪛 Bugfix
• ⚠️ Breaking change (fix or feature that would cause existing functionality to not work as expected)
• 🔃 Refactor of current code

🧪 How Has This Been Tested?

📃 Notes:

✔️ Checklist:

• ⚖️ My code follows the style guidelines of this project
• 👀 I have performed a self-review of my own code
• #️⃣ I have commented my code, particularly in hard-to-understand areas
• 📄 I have made corresponding changes to the documentation
• ⚠️ My changes generate no new warnings
• 🧪 I have added tests to this description that prove my fix is effective or that my feature works
• ⬆️ I increased versions for any altered app according to semantic versioning

➕ App addition

If this PR is an app addition please make sure you have done the following.

• 🖼️ I have added an icon in the Chart's root directory called icon.png

---

Please don't blindly check all the boxes. Read them and only check those that apply.
Those checkboxes are there for the reviewer to see what is this all about and
the status of this PR with a quick glance.

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
-		Generic High Entropy Secret	6e4d56c	charts/stable/sabnzbd/ci/default-values.yaml	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

<sup>🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Our GitHub checks need improvements? Share your feedbacks!</sup>

[ac1dburnz]

I added stuff from my repo by accident. I have corrected them

[ac1dburnz]

@Ornias1993 i made the changes but also had to add one more. The probes dont work on this container, the app builds but i have never had it deploy on my system. I always had to manually disable them on my own catalog. I have disabled them.

[ac1dburnz]