Update the connection data from env on translator creation

[wistefan]

Proposed changes

The change reads out the enviornment variables for connection data on translator connection. This is required, because else the health-check fails until the first real call is made to the api. This leads to a deadlock in k8s environments, since no call is possible before its healthy.

Types of changes

What types of changes does your code introduce to the project? Put an x in the boxes that apply

• [x] Bugfix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [ ] Maintenance (update of libraries or other dependences)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• [x] I have read the CONTRIBUTING doc
• [x] I have signed the CLA
• [ ] I have added tests that prove my fix is effective or that my feature works
• [x] I have run all the existing tests locally (not just those related to my feature) and there are no errors
• [x] After the last push to the PR branch, I have run the lint script locally and there are no changes to the code base
• [x] I have updated the RELEASE NOTES
• [ ] I have added necessary documentation (if appropriate)
• [ ] Any dependent changes have been merged and published in downstream modules

Further comments

"Martel Open Source Software Individual Contributor License Agreement"

"Contributing to QuantumLeap"

"QuantumLeap Release Notes"

[github-actions[bot]]

CLA Assistant Lite bot All contributors have signed the CLA ✍️

[wistefan]

I have read the CLA Document and I hereby sign the CLA

[c0c0n3]

hi @wistefan and welcome on board! Thanks so much for your contrib! I've done a first review, see my comments there. Basically if you've tested the fix we could keep it---I'm just not sure about the read_env call having the effect you're hoping for, so if you could please double check.

Thanks a million!!