Update report version to validate npm secret change (#7148)

#### Details
This is to validate the release secret update
<!-- Usually a sentence or two describing what the PR changes -->

##### Motivation
Quarterly rotation; standard
<!-- This can be as simple as "addresses issue #123" -->

##### Context

<!-- Are there any parts that you've intentionally left out-of-scope for
a later PR to handle? -->

<!-- Were there any alternative approaches you considered? What
tradeoffs did you consider? -->

#### Pull request checklist
<!-- If a checklist item is not applicable to this change, write "n/a"
in the checkbox -->
- [ ] Addresses an existing issue: #0000
- [ ] 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`.
- [ ] (UI changes only) Added screenshots/GIFs to description above
- [ ] (UI changes only) Verified usability with NVDA/JAWS

packages/report/package.json

@@ -1,6 +1,6 @@
 {
     "name": "accessibility-insights-report",
-    "version": "4.7.2",
+    "version": "4.7.3",
     "description": "Accessibility Insights Report",
     "license": "MIT",
     "files": [