[MNT] Add `chromedrive-autoinstaller` for easier local testing

[alyssadai]

Changes proposed in this pull request:

• Running e2e tests locally requires a chromedriver to be in the PATH and for it to be the same version as the currently installed version of Chrome. This process is automated with chromedriver-autoinstaller 🎉, so we no longer need to manually download/upgrade/add to PATH the chromedriver for tests

Checklist

This section is for the PR reviewer

• [x] PR has an interpretable title with a prefix ([ENH], [FIX], [REF], [TST], [CI], [MNT], [INF], [MODEL], [DOC]) (see our Contributing Guidelines for more info)
• [ ] PR links to GitHub issue with mention Closes #XXXX
• [x] Tests pass
• [x] Checks pass

For new features:

• [ ] Tests have been added

For bug fixes:

• [ ] There is at least one test that would fail under the original bug conditions.

[alyssadai]

Thanks for the suggestion @surchs, I'll look into that a bit more.

Would definitely be nice to have an easier way to write Dash unit/e2e tests than Selenium, but I was discouraged by the fact that there's pretty much no Dash docs mentions or discussion posts around using other tools like Cypress (https://community.plotly.com/t/does-plotly-js-play-well-with-cypress-io/32919 and https://community.plotly.com/t/starting-work-on-cypress-e2e-testing-for-dash/34221 were not very promising...).

One thing I've found while writing some of the current tests is that there seem to be minor property discrepancies (?) between the Dash components and normal React components, such that when I've tried to use component locator syntax from non-Dash-specific examples of Selenium tests, they don't always work. ☹️ Unsure how much of this is Dash-specific or just my lack of familiarity with frontend tests. That said, I should probably just try it out locally at some point and confirm.