Don't set jmxremote.authenticate system property by default

[olim7t]

What this PR does:

Which issue(s) this PR fixes:
Fixes #

Checklist

• Changes manually tested
• Automated Tests added/updated
• Documentation added/updated
• CHANGELOG.md updated (not required for documentation PRs)
• CLA Signed: DataStax CLA

[github-actions]

No linked issues found. Please add the corresponding issues in the pull request description.
Use GitHub automation to close the issue when a PR is merged

[sonarqubecloud]

SonarCloud Quality Gate failed.   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
5.5% Duplication

[adejanovski]

By making this change we're changing our defaults. I think we should allow to opt out of having jmx auth enabled instead of changing the default, which will trigger a rolling restart upon upgrade ;)

[olim7t]

By making this change we're changing our defaults. I think we should allow to opt out of having jmx auth enabled instead of changing the default, which will trigger a rolling restart upon upgrade ;)

I don't know, that sounds overkill for such a small change.

[adejanovski]

@olim7t, let's move forward with this, even if we're changing the defaults.
Three things:

• Could you add a changelog entry?
• The unit tests are failing it seems, we'd need to rerun them to see what's going on.
• The PR is still in draft mode.

[adejanovski]

@olim7t, should we close this and fully remove changes we make on the JMX config now that Reaper moved to using the management api?