Fix project selection after changing Jira sites

[GagandeepSingh20]

What Is This Change?

Fixes #1896.

This change fixes the selected Jira project disappearing from the project dropdown after switching Jira sites.

The issue was caused by inconsistent project identifiers:

• Initial project options used project.id.
• Project options loaded after changing sites used project.key.
• The selected project value was still represented by project.id.

Because the dropdown option value and selected project value did not match, the selected project could not be displayed.

This change standardizes the project option value on project.id in the UpdatedSelectedSite reducer path.

A regression test has also been added to verify that, after changing Jira sites, the selected project ID matches the corresponding project option value.

How Has This Been Tested?

Added a focused React unit test covering the UpdatedSelectedSite reducer flow.

The test verifies that:

• Project options use project.id as their value.
• The selected project ID matches the corresponding dropdown option value after changing Jira sites.

Command used:

npm run test:react -- --runTestsByPath \
  src/react/atlascode/create-work-item/utils.test.tsx \
  --runInBand

Result:

Test Suites: 1 passed, 1 total
Tests:       1 passed, 1 total

Basic checks:

• npm run lint
• npm run test

Advanced checks:

• If Atlassian employee & Bitbucket changes: did you test with DC in mind? [See Instructions](https://www.loom.com/share/71e5d17734a547f68fd6128be6cd760e?sid=835e58a7-1240-498d-b2d7-fa7fdf8ffa36)

Recommendations:

• Update the CHANGELOG if making a user facing change

---

Rovo Dev code review: Rovo Dev couldn't review this pull request
The pull request author does not have access to Rovo Dev.

[atlassian-cla-bot]

Hooray! All contributors have signed the CLA.