Remove obsolete secrets from the brig config

[sghosh23]

The secrets are removed/unsupported by wire backend with release 5.4.0: https://github.com/wireapp/wire-server/blob/dd959eb3d5da23bcb6aa83de9cf12d7f6b31b6a1/CHANGELOG.md#release-notes-17

Change type

• Fix
• Feature
• Documentation
• Security / Upgrade

Basic information

• THIS CHANGE REQUIRES A DEPLOYMENT PACKAGE RELEASE
• THIS CHANGE REQUIRES A WIRE-DOCS RELEASE

Testing

• I ran/applied the changes myself, in a test environment.
• The CI job attached to this repo will test it for me.

Offline Build CI (label-based)

Add one or more labels to trigger offline builds:

• build-default - Full production build (ansible, terraform, all packages)
• build-demo - Demo/WIAB build
• build-wiab-staging - WIAB-staging build
• build-min - Minimal build (fastest, essential charts only)
• build-all - Run all three builds

Note: No builds run by default. Add a label to trigger CI.

Tracking

• I added a new entry in an appropriate subdirectory of changelog.d
• I mentioned this PR in Jira, OR I mentioned the Jira ticket in this PR.
• I mentioned this PR in one of the issues attached to one of our repositories.

Knowledge Transfer

• An Asciinema session is attached to the Jira ticket.

Motivation

Objective

Reason

Use case

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[mohitrajain]

jfyi: We don't need bin/secrets.sh, we can mark it deprecated in next commit/pr. I have added a label to build all - this will ensure new artifacts would have cleaner secrets and we can also verify if nothing breaks.