Warn user when using lowercase secrets

[zc-devs]

Follow up #3960 (comment)

Lints

Removed uppercasing all secret env vars, instead, the value of the secrets property is used

[qwerty287]

What does "it might not work properly" work?

It should work. You just have to access it with the lower case name as you defined it.

[zc-devs]

it might not work properly = you have to access it with the lower case name or change secret name in pipeline

Fixed message in b5cf0d0

[6543]

?!? did we not move to case sensitive iand depricate the secret key as a whole ?!?

[zc-devs]

move to case sensitive

Yes, therefore the PR.

depricate the secret key as a whole

No, there was empty deprecation section in the linter code on main when I made the PR and there was no warnings in UI on next and 2.7 in this regard.
It is being discussed #4015.

[qwerty287]

So while I understand that you would like to have a warning, this is an enhancement and therefore shouldn't go into 2.7.x.

[lafriks]

I don't think this is needed as we already will have warning in 3.0 about deprecated secrets section as whole

[qwerty287]

Now with #4235, I agree to @lafriks. However, we plan to do a 2.8.0 release with some important enhancements. We can put this on the list for it and merge it there after we did 2.7.2