[JENKINS-71971][JEP-237] FIPS-140 compliant version of HudsonPrivateSecurityRealm

[divyasivasamy]

JENKINS-71971 Allow the use of HudsonPrivateSecurityRealm with a FIPS compliant password algorithm.

Prior to this change the internal security realm used bcrypt (which uses the blowfish algorithm) to hash passwords. Blowfish is not a FIPS compliant algorithm and as this was used in the initial install it meant a clean install setup via the wizard could never be FIPS-140 compliant.
This addresses that by Implementing an alternative (enabled by a SystemProperty that uses PBKDF2withHmacSHA512.

see also JEP-237

Testing done

To validate the FIPS Mode and create hash of the user password and store it.
to validate a given password during the authentication process against stored hash of the password

Proposed changelog entries

• Developer: Optionally support a FIPS-140 compliant algorithm in the Jenkins' own user database.

Proposed upgrade guidelines

N/A

[github-actions]

Please take a moment and address the merge conflicts of your pull request. Thanks!

[jtnord]

adding security-approved as both @daniel-beck, @Kevin-CB and @yaroslavafenkin have reviewed and left no security related issues (and myself as a cert member 😱 ).

[daniel-beck]

I see no major problems with this PR.

[daniel-beck]

Spotless failed the build.

IMO Spotless means applying PR suggestions has a very small chance of being successful, so should just not be done.

[github-actions]

Please take a moment and address the merge conflicts of your pull request. Thanks!

[jtnord]

failure on windows appears to be the known flake that @jglick and @Vlatombe are tackling in #8534 but is too old to contain the diagnostics from jenkinsci/jenkins-test-harness#657

[welcome]

Congratulations on getting your very first Jenkins core pull request merged 🎉🥳

This is a fantastic achievement, and we're thrilled to have you as part of our community! Thank you for your valuable input, and we look forward to seeing more of your contributions in the future!

We would like to invite you to join the community chats and forums to meet other Jenkins contributors 😊
Don't forget to check out the participation page to learn more about how to contribute to Jenkins.

[MarkEWaite]

Congratulations on the merged pull request @divyasivasamy. Much appreciated!

In future pull requests, it would be best if you retained the formatting from the pull request template so that the automatic changelog generation process works as expected. I've inserted the headings into the pull request description and will confirm that the automatic changelog generation accepts the pull request, but it would be nice in future pull requests if automatic changelog maintenance could do the work instead of a person needing to do the work.