[Theme] Add error handling when development theme role gets mismatched

[jamesmengo]

WHY are these changes introduced?

Following up on

• [Bug]: shopify theme dev is losing track of the development theme #3715

I want to open this PR as a forum for discussion

• Do we even want to add this code since its only purpose is to help reset ephemeral data? (The local data lasts 7 days AFAIK) Docs
• Currently, I'm only adding this guard to findAndCreate which means that

WHAT is this pull request doing?

How to test your changes?

Post-release steps

Measuring impact

How do we know this change was effective? Please choose one:

• n/a - this doesn't need measurement, e.g. a linting rule or a bug-fix
• Existing analytics will cater for this addition
• PR includes analytics changes to measure impact

Checklist

• I've considered possible cross-platform impacts (Mac, Linux, Windows)
• I've considered possible documentation changes
• I've made sure that any changes to dev or deploy have been reflected in the internal flowchart.

[github-actions]

Thanks for your contribution!

Depending on what you are working on, you may want to request a review from a Shopify team:

• Themes: @shopify/advanced-edits
• UI extensions: @shopify/ui-extensions-cli
  • Checkout UI extensions: @shopify/checkout-ui-extensions-api-stewardship
• Hydrogen: @shopify/hydrogen
• Other: @shopify/app-management

[github-actions]

Coverage report

St.❔	Category	Percentage	Covered / Total
🟡	Statements	71.81%	6947/9674
🟡	Branches	68.78%	3423/4977
🟡	Functions	71.24%	1863/2615
🟡	Lines	73.11%	6547/8955

Test suite run success

1637 tests passing in 764 suites.

Report generated by 🧪jest coverage report action from b068f0a

[jamesmengo]

Changing the local key instead in #3798