chore: Enzyme replacement in test files- PR 1 of 6 for part 2 of 3

[v-singhanjal]

Details

Enzyme replacement in files under src/tests/unit/tests/DetailsView/components

Motivation

Existing story: User Story 2136480

Replaced the use of Enzyme in the below files:

1. react-extension-point.test.tsx
2. named-fc.test.tsx
3. index.test.tsx
4. current-view.test.tsx
5. telemetry-common-fields.test.tsx
6. telemetry-messages-list.test.tsx
7. telemetry-viewer.test.tsx
8. debug-tools-nav.test.tsx
9. debug-tools-view.test.tsx
10. stores-tree.test.tsx
11. preview-features-container.test.tsx
12. scoping-container.test.tsx
13. auto-detected-failures-dialog-settings.test.tsx
14. high-contrast/high-contrast-settings.test.tsx
15. issue-filing-settings.test.tsx
16. save-assessment-dialog.test.tsx
17. telemetry-settings.test.tsx
18. settings-panel.test.tsx
19. assessment-left-nav.test.tsx
20. details-view-left-nav.test.tsx

Code coverage before and after codeshift checked and it is same.

Context

Pull request checklist

• Addresses an existing issue: 2136480
• Ran yarn fastpass
• Added/updated relevant unit test(s) (and ran yarn test)
• Verified code coverage for the changes made. Check coverage report at: <rootDir>/test-results/unit/coverage
• PR title AND final merge commit title both start with a semantic tag (fix:, chore:, feat(feature-name):, refactor:). See CONTRIBUTING.md.
• [n/a] (UI changes only) Added screenshots/GIFs to description above
• [n/a ] (UI changes only) Verified usability with NVDA/JAWS

[madalynrose]

A couple small nits and then this looks good to go!

[DaveTryon]

General comment: Having a series of PR's titled "... user story ABC", "... user story DEF", "...user story GHI", etc., can be useful when tracking the implementation of the work, but once the PR is merged, its value drops dramatically, especially if the engineering system ever becomes unavailable. As an alternative, may I suggest a slightly different approach, with the intent to make it possible to understand the change even without access to the ADO system (which will be the case for any external contributor, or even internal contributors should we later change engineering systems)

• The title should capture the fact that this is part of a broader set of tasks. All tasks in the set will ideally use the same pattern
• The description should still point to the ADO item, but will also include the set of work included in this task. There will be some duplication with ADO--that's a good thing.

So a specific one of these tasks might have a title of "chore: Enzyme replacement in test files - part 3 of 12". The description might include something like:

Files in scope for this PR:

• src/tests/unit/tests/DetailsView/components/awesome-class.test.tsx
• src/tests/unit/tests/DetailsView/components/amazing-component.test.tsx
• src/tests/unit/tests/DetailsView/components/incredible-navigation.test.tsx
  etc.