Add services and restructure OIDC Gudies to be more consistant

[Nerdtality]

Description

This PR adds services and restructures OIDC Guides to be more consistant

I did have to use AI to help point out issues and improvements and merge new changes as they came in

Cleanup inconsistencies in verbiage and instructions
Clear separation between app configuration and VoidAuth configuration
Added references to release notes and setup discussions where relevant
Every application now has a link to its official documentation where available
Linked to specific OIDC/OAuth setup guides
Got straight to the configuration with clear, concise headers
Removed unnecessary setup prose
"Auth Method" (not "Authentication Method")
"Client Secret" (capitalized consistently)
"Redirect URLs" (standardized plural)
"PostLogout URL" (CamelCase)
Every section uses identical header: "VoidAuth OIDC Client Configuration:"
Every app now follows the same pattern: intro > configuration > VoidAuth section > notes/tips
Fields in consistent order: Client ID > Auth Method > Client Secret > Redirect URLs > PostLogout URL
Consistent placement of external documentation links
All notes properly formatted with markdown alerts
Optional fields always marked with comments
Comments standardized with # prefix
Consistent use of colons for key-value pairs
All environment variables now use quotes and proper bash syntax highlighting

Added services:
Jellyseer
ByteStash
Dockhand

Related Tickets & Documents

N/A

Screenshots

See Markdown Preview

[Nerdtality]

There are a lot of changes here and likely needs a sanity check, not sure if it looks better either so feel free to close without merging if needed. If you like it, it may also be beneficial to create a guide/template to help others also stay consistent. I think there are also other edits I would like to suggest but let's see where this goes.

[notquitenothing]

There are a lot of changes here and likely needs a sanity check, not sure if it looks better either so feel free to close without merging if needed. If you like it, it may also be beneficial to create a guide/template to help others also stay consistent. I think there are also other edits I would like to suggest but let's see where this goes.

I will review and let you know what I think 😊 I am currently making some wording changes that may need to be incorporated even if everything else looks good (consistently using 'OIDC App' when talking about what you create/update in VoidAuth)

[Nerdtality]

Conflict resolved

Also,

**VoidAuth OIDC Client Configuration:**
Changed back to
**In VoidAuth OIDC App Page:**
since that was already done previously and I did not catch that

[Nerdtality]

Question, would WebP (better version of GIF) be better than PNG/JPEG for screenshots or demonstrations?

[notquitenothing]

Question, would WebP (better version of GIF) be better than PNG/JPEG for screenshots or demonstrations?

WebP would probably be better, but it doesn't make any sense to convert existing images in my opinion since those original images will be stored in the git repo in commit history anyways. If any images were very large and causing slowdown when loading the docs page that could be an exception.

[Nerdtality]

Question, would WebP (better version of GIF) be better than PNG/JPEG for screenshots or demonstrations?

WebP would probably be better, but it doesn't make any sense to convert existing images in my opinion since those original images will be stored in the git repo in commit history anyways. If any images were very large and causing slowdown when loading the docs page that could be an exception.

I was thinking more of the lines of me going thru all of these and making step>step>step animations on the most difficult ones. But rethinking through this, it would cause more work for others in the future.

[notquitenothing]

After review the changes look great, and I will merge the PR soon

[Nerdtality]

Really quick question, on some of the Environment Variables, was it intentional to have ```bash instead of ```YAML ?