remove vault-approle-token from docker secrets

[daisieh]

This gets rid of the warnings from Vault about our approle token ID not being secure. It also removes yet another of our docker secrets.

On a fresh build, should pass integration tests.

[mshadbolt]

I am still seeing the warning on a fresh build

Error logs for vault:
--------------------
354     time="2024-10-25T14:47:39-07:00" level=warning msg="Found orphan containers ([candigv2_keycloak_1 candigv2_fluentd_1]) for this project. If you removed or renamed this service in your compose file, you can run this command with the --remove-orphans flag to clean it up."
447     {"request_id":"71aec515-4d85-3685-0c56-fd35cfb39a32","lease_id":"","renewable":false,"lease_duration":0,"data":null,"wrap_info":null,"warnings":["Supplying a custom ID for the token uses the weaker SHA1 hashing instead of the more secure SHA2-256 HMAC for token obfuscation. SHA1 hashed tokens on the wire leads to less secure lookups.","Endpoint ignored these unrecognized parameters: [periodic]"],"auth":{"client_token":"1Y8ep9ahhhjtiCB5w8I7zA","accessor":"OwqVIfBHJ05uU86FzOE03Xg0","policies":["approle","default"],"token_policies":["approle","default"],"metadata":null,"lease_duration":2764800,"renewable":true,"entity_id":"","token_type":"service","orphan":false,"mfa_requirement":null,"num_uses":0}}
--------------------

[mshadbolt]

ignore previous comment, works perfectly for me when I use the actual branch

[mshadbolt]

working for me, no more warning