fix(forms): Include :orgId in new provider form route for search

[sentry]

This PR fixes an issue where navigating to the "New Provider" form via Settings Search resulted in a "Route not found" error.

The root cause was that the <FormSearch> component in static/app/views/settings/featureFlags/changeTracking/newProviderForm.tsx defined its route prop as /settings/feature-flags/change-tracking/new-provider/, omitting the required :orgId segment.

This incomplete route was then picked up by the Settings Search index (generatedFieldRegistry.ts), leading to an invalid URL being generated for the search result.

The fix involves:

1. Updating the route prop in newProviderForm.tsx to /settings/:orgId/feature-flags/change-tracking/new-provider/.
2. Regenerating and committing the generatedFieldRegistry.ts file to reflect this change.

This ensures that the Settings Search correctly registers and generates valid URLs for the "New Provider" form.

Legal Boilerplate

Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.

Fixes JAVASCRIPT-3B75

_{Comment @sentry <feedback> on this PR to have Autofix iterate on the changes.}

[getsantry]

This issue has gone three weeks without activity. In another week, I will close it.

But! If you comment or otherwise update it, I will reset the clock, and if you remove the label Waiting for: Community, I will leave it alone ... forever!

---

"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀