Implement central release plugin and version updates

[jonathanaustin]

• Included central-publishing-maven-plugin in release profile to publish to maven central
• Update bordertech-parent and qa-parent pom.xml plugins to latest version
• Moved dependency-check-maven plugin into own profile check-dep as it requires JDK11
• Moved javadoc plugin into the release profile so only created when doing a release

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[github-advanced-security]

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

• The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
• Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
• You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.