Testing, BugFixes and Review Improvements

- Fix SabNZBD hostname whitelist issues
- Add transmission settings to GUI
- Fix some qbittorrent connection issues
- Remove Torrent Ingress
- Fix some device mounting gui issues
- Change repo url references
- Cleaning up the homepage
- Drop Deluge (App is not safe due to being mostly abandoned)
- Move Emby to own Non-Root container
- Create new trains and move charts->stable
- Add Plex app
- update emby and plex intel hardware support
- Implement new parallel CI for Apps
- Move PGID, PUID, TZ and UMASK settings to "Container Image" configuration
- Stop running some workflows on staging
- Add branch security trigger to matrix workflows

Co-authored-by: Troy Prelog <35702532+tprelog@users.noreply.github.com>

docs/development/chart-yaml-structure.md

@@ -1,7 +1,7 @@
 # Chart.yaml layout
 
 At TrueCharts we try to keep some files standardised, this enables us to make changes to these charts in bulk with less risk of mistakes. Chart.yaml is one of these files.
-In this documentation we will explain the standardised layout options. For an example layout, please see our standard Chart.yaml [template](https://github.com/truecharts/charts/tree/master/.tools/templates/chart/Chart.yaml)
+In this documentation we will explain the standardised layout options. For an example layout, please see our standard Chart.yaml [template](https://github.com/truecharts/apps/tree/master/.tools/templates/chart/Chart.yaml)
 
 
 ### Layout Explained
@@ -44,7 +44,7 @@ annotations:
 
 In the above description there are a lot of values that are not actually used. Some of those, like `deprecated`, we just set to false. While others, like `annotations` get commented out.
 
-Please refer to our standard Chart.yaml [template](https://github.com/truecharts/charts/tree/master/.tools/templates/chart/Chart.yaml) to see which unused values needs which treatment.
+Please refer to our standard Chart.yaml [template](https://github.com/truecharts/apps/tree/master/.tools/templates/chart/Chart.yaml) to see which unused values needs which treatment.
 
 ##### Dependencies
 
@@ -55,7 +55,7 @@ All other dependencies are expected to be listed in alphabetical order.
 ##### Maintainers
 
 The first maintainer should always be TrueCharts, as the TrueCharts core team is expected to step in if the other maintainers fail to maintain their work.
-An example of how to list TrueCharts as a maintainer is available in our standard Chart.yaml [template](https://github.com/truecharts/charts/tree/master/.tools/templates/chart/Chart.yaml).
+An example of how to list TrueCharts as a maintainer is available in our standard Chart.yaml [template](https://github.com/truecharts/apps/tree/master/.tools/templates/chart/Chart.yaml).
 
 While currently we primarily use the CODEOWNERS file to define maintainers. We might in the future either automate keeping track of maintainers, completely rely on the maintainers or do both. For this reason it's important to add yourself as a maintainer if you expect to maintain your work.
 All other maintainers are, ofcoarse, expected to be entered in importance. With the primary maintainer under "truecharts" and secondary maintainers thereunder.

docs/development/containers/index.md

@@ -17,4 +17,4 @@ For configuration and documentation see [here](https://truecharts/containers/get
 
 We have several different methods for getting support.
 
-- [GitHub Discussions](https://github.com/truecharts/charts/discussions)
+- [GitHub Discussions](https://github.com/truecharts/apps/discussions)

docs/development/getting-started.md

@@ -20,7 +20,7 @@ You will need these to start your journey:
 
 ### Setting up your dev environment
 
-If you already know what you're doing, go to our [GitHub](https://github.com/truecharts/charts) and fork. Otherwise, look at this picture, from now on this will be the **contribution cycle**. This is how our workflow will look at the end of the tutorial.
+If you already know what you're doing, go to our [GitHub](https://github.com/truecharts/apps) and fork. Otherwise, look at this picture, from now on this will be the **contribution cycle**. This is how our workflow will look at the end of the tutorial.
 
 <img src="https://i.imgur.com/qPg9XmQ.png" alt="Contribution cycle" style="zoom:120%;" />
 
@@ -28,7 +28,7 @@ If you already know what you're doing, go to our [GitHub](https://github.com/tru
 
 What's that? You have no idea what any of that means? Worry not, my fellow contributor! I will guide you step by step.
 
-First, you did your [GitHub account](https://github.com/) account as suggested, right? Good. We will now visit the [TrueCharts  Repository in GitHub](https://github.com/truecharts/charts) and click this little button located at the top right corner of the page:
+First, you did your [GitHub account](https://github.com/) account as suggested, right? Good. We will now visit the [TrueCharts  Repository in GitHub](https://github.com/truecharts/apps) and click this little button located at the top right corner of the page:
 
 ![Fork button](https://i.imgur.com/lw1XYPS.png)
 
@@ -78,7 +78,7 @@ Are you done downloading? Awesome! Now your local repo is automagically soul-lin
 
 |       GitHub Desktop       |                           Git Bash                           |
 | :------------------------: | :----------------------------------------------------------: |
-| This is automagically done | Navigate to the folder where your local repo is<br />``git remote add upstream https://github.com/truecharts/charts.git``<br />Now to make sure everything is in order, we do<br />``git remote -v``<br />and it should show both repos, yours in **origin** and central in **upstream** |
+| This is automagically done | Navigate to the folder where your local repo is<br />``git remote add upstream https://github.com/truecharts/apps.git``<br />Now to make sure everything is in order, we do<br />``git remote -v``<br />and it should show both repos, yours in **origin** and central in **upstream** |
 
 
 ##### Setting up Pre-Commit
@@ -142,7 +142,7 @@ Now all that is missing is publishing your commits to your remote (**origin**)
 
 #### Making a PR
 
-A **P**ull **R**equest is the only way to get your changes into the central version of the game. You do a PR by **committing** your changes and **pushing them** to your remote repo (**origin**). Then, visit the [TrueCharts Repository in GitHub](https://github.com/truecharts/charts) and click this green button:
+A **P**ull **R**equest is the only way to get your changes into the central version of the game. You do a PR by **committing** your changes and **pushing them** to your remote repo (**origin**). Then, visit the [TrueCharts Repository in GitHub](https://github.com/truecharts/apps) and click this green button:
 
 ![make a pr button](https://i.imgur.com/yt2QJd4.png)