fix(jira): rename "Jira Server" to "Jira Data Center" in UI labels

[bujjibabukatta]

Summary

Renames the user-facing label "Jira Server" to "Jira Data Center" across the Jira plugin UI, reflecting Atlassian's official deprecation and rebranding of the product.

Changes

• config-ui/src/plugins/register/jira/connection-fields/auth.tsx — updated radio button label and endpoint URL hint text
• config-ui/src/plugins/register/jira/config.tsx — updated rate limit help text

What was intentionally left unchanged

Internal Go identifiers (JiraServerInfo, DeploymentServer) and the database table name (_tool_jira_server_infos) were not renamed. These are internal implementation details and renaming them would require a database migration, which is out of scope for a UI label fix.

Does this close any open issues?

Closes #8856

[bujjibabukatta]

Hi @klesh could you please approve pull request?

[klesh]

Hello. I am unable to proceed because the code you submitted does not correspond to your description or the issue you are referencing.

[klesh]

Please update your title to a more descriptive one.

[bujjibabukatta]

Hi @klesh, apologies for the confusion. I've removed the unrelated Jenkins commit from the branch — the PR now contains only the 3 UI label changes for the Jira rename. I've also updated the PR title to be more descriptive. Please let me know if anything else needs to be addressed.

[klesh]

We could rename it to Data Center, but we should also keep the Server label because some might still be using an older Jira Server instance.
And, you need to update the https://github.com/apache/devlake-website repository as well.

[bujjibabukatta]

Hi @klesh ,
Thanks for the feedback. Just to confirm — should I update the radio label to "Jira Server / Jira Data Center" while keeping value="server" unchanged, or would you prefer a separate radio option for Jira Data Center? I want to make sure I implement exactly what you have in mind before making changes.

Regarding the devlake-website update — I'll raise a separate PR on the devlake-website repository for the documentation changes. Should I wait for this PR to be approved first before doing that, or can I proceed in parallel?