Change Bitbucket server URL validation endpoint to support bitbucket 9+

[LividSquid]

This PR contains changes that I believe will address the issues in these community posts: SonarQube with Bitbucket 9.0 and Sonarqube is missing the Authorization token for Bitbucket DC.

I changed the validateUrl function to use the /status endpoint. This endpoint returns a json object containing the current state of Bitbucket (e.g. {"state":"RUNNING"}), so I created the State class to read that into. Lastly, I updated the validate_url_success test to test against an expected response.

Since I started working on this, SONAR-23470 has been created to address the issue internally within SonarSource.

I built the application twice: once directly from the master branch with no changes, and once with my changes. I then configured the Bitbucket integration using the same token on both.

Master:

==> /Users/lividsquid/sq/sonarqube/sonar-application/build/distributions/sonarqube-10.8-SNAPSHOT/logs/web.log <==
2024.10.24 17:18:00 INFO  web[b75b4eae-a2c6-4250-af7f-f970b4c54add][o.s.a.c.b.BitbucketServerRestClient] Unable to contact Bitbucket server: 401 com.atlassian.plugins.rest.api.security.exception.AuthenticationRequiredException You are not permitted to access this resource

This branch: