Support token with jira-report

### New feature, improvement proposal

jira-report auth regression in the 3.x milestone

The auth support in the jira-report has room for improvement. Similar to #86 the jira-report should be changed to support tokens only. Atlassian has similarly [deprecated](https://developer.atlassian.com/cloud/confluence/deprecation-notice-basic-auth/) basic auth.

This looks to no longer be true, auth can be required on this endpoint.
https://github.com/apache/maven-changes-plugin/blob/25fb83c96d6d9f3333ef205974b1cd89aded650c/src/main/java/org/apache/maven/plugins/changes/jira/RestJiraDownloader.java#L415-L420

The client setup looks to have removed the maintain session context when uplifted. Which if the report is changed to token only, would no longer be relevant.
https://github.com/apache/maven-changes-plugin/blob/25fb83c96d6d9f3333ef205974b1cd89aded650c/src/main/java/org/apache/maven/plugins/changes/jira/RestJiraDownloader.java#L753

https://github.com/apache/maven-changes-plugin/blob/c2d9d4573f32325fa355e972bfc748b5fae77177/src/main/java/org/apache/maven/plugin/jira/RestJiraDownloader.java#L565

Start with the authentication and client setup in src/main/java/org/apache/maven/plugins/changes/jira/RestJiraDownloader.java around lines 415-420 and 753, then compare the older implementation linked in the issue. Trace how jira-report currently authenticates and identify the relevant project checks. Done means the report supports token-only authentication without relying on the removed maintain-session context.

Written by the indexing model from the issue text.