Set DB environment for java+ as well as for java

[jhorvath]

To correctly set environment variables for database connection we need to register DBConfigurationProvider for both targets - java+ and java.

[sdedic]

I would suggest to make 2 instances of DBConfigurationProvider instead of using a global variable -- but it seems a matter of style here: none of the reloadable NBLS-related state is used.

[neilcsmith-net]

@jhorvath only the release team should be merging to delivery.

[neilcsmith-net]

cc/ @mbien out of interest, when you were setting up branch protection, did you notice whether asf.yml exposed the ability to restrict committing on certain branches to certain accounts?

[MartinBalin]

@jhorvath only the release team should be merging to delivery.

@neilcsmith-net sorry, I've suggested to Jan he should merge to delivery.

[neilcsmith-net]

@MartinBalin no worries - you're on it anyway. I'll be syncing for rc2 tomorrow morning, so unless there's anything urgent let's wait for both sync PRs before merging anything else.

[mbien]

cc/ @mbien out of interest, when you were setting up branch protection, did you notice whether asf.yml exposed the ability to restrict committing on certain branches to certain accounts?

@neilcsmith-net I don't think this is possible. The doc at least does not list this as an option.

edit: gh itself seems to be supporting it: https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/managing-protected-branches/about-protected-branches#restrict-who-can-push-to-matching-branches

going to ask on infra slack