feat(rome_js_analyze): use exhaustive deps support properties

[xunilrj]

Summary

This PR allows useExhaustiveDependencies to support properties. This opens three new possibilities:

• we correctly specify the property as dependency;
• we specify a more generic dependency;
• we specify a more specific dependency.

Test Plan

> cargo test -p rome_js_analyze -- exhaustive

[netlify]

✅ Deploy Preview for docs-rometools canceled.

Name	Link
🔨 Latest commit	ce04744
🔍 Latest deploy log	https://app.netlify.com/sites/docs-rometools/deploys/637e8c1335a782000973d041

[github-actions]

Playground for commit 88063b0

[ematipico]

Not related to this PR, and I don't expect to be implemented in this PR. I was wondering if we should actually use the range that starts from the hook name and finishes at ), because the issue is the whole hook, not just the name.

// from start range of `useEffect`
useEffect(() => {
	return a + 1;
}, [a]);
// to the range of the last token `)`

This is a suggestion for all the diagnostics obviously. What do you think?

[xunilrj]

I personally tend to dislike ranges too big. Because don't focus your attention, and is horrible in the IDE. But we can do, if everyone else prefers.

[calibre-analytics]

Comparing feat(rome_js_analyze): use exhaustive deps support properties Snapshot #1 to median since last deploy of rome.tools.

	LCP?	CLS?	TBT?
Overall Median across all pages and test profiles	2.2s  from 258ms	0.0 no change	173ms no change
Chrome Desktop Chrome Desktop • Cable	2.2s  from 258ms	0.0 no change	358ms  from 22ms
iPhone, 4G LTE iPhone 12 • 4G LTE	1.1s  from 239ms	0.0 no change	11ms no change
Motorola Moto G Power, 3G connection Motorola Moto G Power • Regular 3G	17s  from 1.06s	0.0 no change	173ms no change

1 page tested

 Home

Browser previews

Chrome Desktop	iPhone, 4G LTE	Motorola Moto G Power, 3G connection

Most significant changes

	Value	Budget
JS Parse & Compile Motorola Moto G Power, 3G connection	1.78s  from 27ms
Total JavaScript Size in Bytes Chrome Desktop	5.35 MB  from 86.8 KB
Total JavaScript Size in Bytes iPhone, 4G LTE	5.35 MB  from 86.8 KB
Total JavaScript Size in Bytes Motorola Moto G Power, 3G connection	5.35 MB  from 86.8 KB
JS Parse & Compile iPhone, 4G LTE	502ms  from 10ms

_{27 other significant changes: JS Parse & Compile on Chrome Desktop, Total Blocking Time on Chrome Desktop, Largest Contentful Paint on Motorola Moto G Power, 3G connection, First Contentful Paint on Motorola Moto G Power, 3G connection, Time to Interactive on Motorola Moto G Power, 3G connection, Total CSS Size in Bytes on Chrome Desktop, Total CSS Size in Bytes on iPhone, 4G LTE, Total CSS Size in Bytes on Motorola Moto G Power, 3G connection, Total Page Size in Bytes on Chrome Desktop, Total Page Size in Bytes on iPhone, 4G LTE, Total Page Size in Bytes on Motorola Moto G Power, 3G connection, Time to Interactive on Chrome Desktop, Number of Requests on Motorola Moto G Power, 3G connection, Number of Requests on Chrome Desktop, Number of Requests on iPhone, 4G LTE, Largest Contentful Paint on Chrome Desktop, First Contentful Paint on Chrome Desktop, Speed Index on Motorola Moto G Power, 3G connection, Time to Interactive on iPhone, 4G LTE, Largest Contentful Paint on iPhone, 4G LTE, First Contentful Paint on iPhone, 4G LTE, Speed Index on Chrome Desktop, Total HTML Size in Bytes on Chrome Desktop, Total HTML Size in Bytes on iPhone, 4G LTE, Total HTML Size in Bytes on Motorola Moto G Power, 3G connection, Lighthouse Performance Score on Motorola Moto G Power, 3G connection, Lighthouse Performance Score on Chrome Desktop}

_{Calibre: Site dashboard | View this PR | Edit settings | View documentation}