docs: update credentials section for org-level secrets

- All secrets are now managed at organization level
- Remove outdated "Read and write permissions" requirement
- Remove release bot secrets (not used by template workflows)

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

Author: cuioss-oliver

README.adoc

@@ -68,25 +68,19 @@ The key must *not* contain spaces. They are used for creating urls as well.
 
 === Credentials
 
-Add the necessary credentials to the project: "Settings" -> "Secrets" -> "Actions", as there are: 
+All required secrets are managed at the **organization level** and automatically inherited by repositories in the cuioss organization:
 
-* `GPG_PASSPHRASE` -> Code Signing
-* `GPG_PRIVATE_KEY` -> Code Signing
-* `OSS_SONATYPE_PASSWORD` -> Deploy to maven-central 
-* `OSS_SONATYPE_USERNAME` -> Deploy to maven-central
-* `PAGES_DEPLOY_TOKEN` -> Deploying the result of maven site to https://cuioss.github.io
-* `SONAR_TOKEN` -> Sonar-Cloud
+* `GPG_PASSPHRASE` / `GPG_PRIVATE_KEY` - Code signing
+* `OSS_SONATYPE_USERNAME` / `OSS_SONATYPE_PASSWORD` - Maven Central deployment
+* `PAGES_DEPLOY_TOKEN` - GitHub Pages deployment
+* `SONAR_TOKEN` - SonarCloud analysis
 
-They are picked up in the predefined pipeline-configurations:
+No repository-level secret configuration is needed.
 
-* `.github/workflows/maven.yml`
-* `.github/workflows/maven-release.yml`
+For reference:
 
-Ensure that the actions are authorized correctly: Settings > Actions > General > Workflow permissions >  "Read and write permissions" must be selected *not* "Read repository contents permission"
-
-Documentation on how to create a signing key can be found https://github.com/cuioss/cui-parent-pom/blob/master/doc/signing_key.adoc[Documentation at cui-parent-pom] 
-
-A sonar token can be derived from https://sonarcloud.io/account/security
+* Signing key documentation: https://github.com/cuioss/cui-parent-pom/blob/master/doc/signing_key.adoc[Documentation at cui-parent-pom]
+* SonarCloud tokens: https://sonarcloud.io/account/security
 
 === Further Steps