[Settings]Fix links to the Text Extractor page

[jaimecbernardo]

Summary of the Pull Request

On 0.80.0, links from Text extractor util to its Settings page or from PowerToys plugin of PT Run were broken.
This seems to have been caused by the change from "PowerOCR" to "PowerOcr" to help in the DSC PR.
This PR converts the other strings that stayed as "PowerOCR" to "PowerOcr".

PR Checklist

• Closes: Text Extractor: open settings is buggy #32352
• Communication: I've discussed this with core contributors already. If work hasn't been agreed, this work might be rejected
• Tests: Added/updated and all pass
• Localization: All end user facing strings can be localized
• Dev docs: Added/updated
• New binaries: Added on the required places
  • JSON for signing for new binaries
  • WXS for installer for new binaries and localization folder
  • YML for CI pipeline for new test projects
  • YML for signed pipeline
• Documentation updated: If checked, please file a pull request on our docs repo and link it here: #xxx

Validation Steps Performed

From Text Extractor util, press the settings button and verify it opens Settings in the Text Extractor page.
From PT Run PowerToys plugin, search for Text Extractor and press the Settings button.
From Dashboard, press the Text Extractor entry and verify it opens the Text Extractor Settings page.
From OOBE, press the button that opens the Text Extractor settings page.

[davidegiacometti]

LGTM!
Tested in Text Extractor, Dashboard, OOBE, Run and it's working as expected.

[Jay-o-Way]

A basic search for "PowerOCR" (case sensitive) returns a lot of results. For one example in launcher ... UtilityHelper.cs --> SettingsDeepLink.SettingsWindow? GetSettingsWindow(UtilityKey key)
Apparently, this does work nicely - and therefore not needed here. Would it make sense to align this syntax, though?

[jaimecbernardo]

A basic search for "PowerOCR" (case sensitive) returns a lot of results. For one example in launcher ... UtilityHelper.cs --> SettingsDeepLink.SettingsWindow? GetSettingsWindow(UtilityKey key) Apparently, this does work nicely - and therefore not needed here. Would it make sense to align this syntax, though?

One is the strings passed around and the other is the Enum identifier. Perhaps aligning would be good, but for a hotfix I prefer as little change as possible to reduce the surface that might have errors.