AWS and Azure broker docu-checker resource naming fixes (kyma#5185)

[m-wcislo]

Description

Changes proposed in this pull request:

• limit resource names created in aws and azure brokers charts to max 63 chars. Docu-checker templates/resources were possibly violating 63 chars constraints.

Related issue(s)
Fixes kyma-project/kyma#5185

Tested/verified only with Azure.

[kyma-bot]

Hi @m-wcislo. Thanks for your PR.

PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[CLAassistant]

All committers have signed the CLA.

[mszostok]

/ok-to-test

[mszostok]

/test all

[mszostok]

Hi @m-wcislo, thanks for your contribution!

At the beginning, I thought about doing that by new def in _helpers.tpl file to make it DRY but after a while IMO for now, it's good enough to have it like that, so /lgtm

[m-wcislo]

Yes, I also thought about helper but then better solution would be to handle the fullname/release generation in general in better way maybe. In fact by truncating fullname we are limiting uniqueness. So I wanted to know your opinion, but it is fine as "quickfix" i guess.