This will allow the versions to be kept up to date automatically by DA within PNC.
A side effect is fixing issues like KEYCLOAK-7896.
Also remove additional dependencyExclusions that can be filled by PME BOMREST
This causes the community profile to be disabled in the product build.
The product profile is active already, but unfortunately maven doesn't allow
chained profile activation, so there's no way to automatically disable the
community profile when the product profile is active.
An alternative solution would have been to add `-Dproduct` to the properties
list, but then it wouldn't be clear what was trying to be done with the extra
argument.
I've checked with `git grep -B3 '!product'`, and the only profiles that use the
`!product` property activation condition are the community profiles.
This adds a json file with the arguments for maven and PME. Variables are
included for the product build pipeline to fill in with appropriate internal
values.
The community build is unaffected by this change.
