Improve Error Message for Environment Variable Injection Conflicts

[matthewchivers]

This PR improves the error message logged when not all environment variables can be successfully injected. I believe the updated message provides clearer information about potential conflicts with existing environment variables that may have the same name.

The cause of this error was not immediately obvious to me when reviewing failures in Jenkins output - so this is just a slight improvement to the error message (subjective).

Changes:

• Updated the error message in EnvInjectEnvVarsContributor.java to clarify that conflicts with existing environment variables may be the reason for injection failures.

Testing done

No logic changes - just error output. Tests already exist for this functionality.

Submitter checklist

• Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
• Ensure that the pull request title represents the desired changelog entry
• Please describe what you did
• Link to relevant issues in GitHub or Jira
  • None
• Link to relevant pull requests, esp. upstream and downstream changes
  • None
• Ensure you have provided tests - that demonstrates feature works or fixes the issue
  • Existing tests cover these lines

[matthewchivers]

Is there anything more that I need to do to get this looked at please?

Perhaps I needed to approach this differently? I'm unfamiliar with contribution guidelines on this project.

[matthewchivers]

Hi @NotMyFault, I’ve noticed you’ve been active recently. When you have a moment, could you please take a look at this PR? Any feedback or guidance on how I can help move this forward would be much appreciated. Thanks in advance!

[matthewchivers]

Closing, as I don't wish to chase this further.