Pin axe-core version to patch updates only (`~`)

[straker]

A user recently ran into a problem where they installed an api at v4.7 but got axe-core version v4.8 (causing some confusion on why rules weren't running that should have been). Turns out that we've been pinning to axe-core using ^ which allows minor updates. This goes against our goal of version locking the apis to the major and minor version of axe-core that is used in the api.

We'll fix this by using ~ to patch pin our axe-core dependency.

[padmavemulapati]

Here validated the scenarios:

1. With Production version of axe-core-npm packages(4.7.0), holding a axe-core version 4.7.2 (old version) with ^ in dependencies.

in the output it is getting the axe-core version with latest axe-core(4.8.2) because of the dependency specified as ^ so it allowing the next to 4.7.2 all minor versions.

2. With Production version of axe-core-npm pacakges(4.7.0), holding a axe-core version 4.7.2(old version) without ^ in the dependencies.

in the output it is getting the axe-core version with (4.7.2) because of the dependency specified without ^ it is strictly considering the specified version and not allowing the next to 4.7.2 all minor versions.

3. With the latest canary version of axe-core-npm packages(4.7.4-f03670b.0), and with (4.7.2) because of the dependency specified without ^ it is strictly considering the specified version and not allowing the next to 4.7.2 all minor versions.

in the output it is getting the axe-core version with (4.7.2) because of the dependency specified without ^ it is strictly considering the specified version and not allowing the next to 4.7.2 all minor versions.

4. With the latest canary version of axe-core-npm packages(4.7.4-f03670b.0) , and with latest (4.8.2) because of the dependency specified without ^ it is strictly considering the specified version and not allowing the next to 4.8.2 all minor versions.

in the output it is getting the axe-core version with (4.8.2) because of the dependency specified without ^ it is strictly considering the specified version and not allowing the next to 4.8.2 all minor versions.

without `^` symbol if axe-core version is 4.7.2 (old version) with Prod version of axe-core/npm packages

webdriverjs

webdriverjs4.7.2.mov

webdriverio

webdriverio4.7.2.mov

cli

CLI4.7.2.mov

puppeteer

puppeteer4.7.2.mov

playwriught

playwright4.7.2.mov

Axe-core4.7.2 with ^ symbol holding next minor versions even axe-core/npm verskons are latest.

cli

CLI4.7.2with.Symbol.mov

playwright

playwright4.7.2with.symbol.mov

puppeteer

puppeteer4.7.2with.symbol.mov

webdriverio

webdriverio4.7.2with.symbol.mov

webdriverjs

webdriverjs4.7.2.symbol.mov

axe-core/npm canary versions and event not installing the latest axe-core, as it implemented with latest axe-core all packages holding axe-core latest version.

cli

CLI-cannarywithoutInstallingaxe-corelatest.mov

webdriverio

webdriverio-canarywithoutaxecorelatest.mov

webdriverjs

Screen.Recording.2023-10-12.at.10.22.46.AM.mov

puppeteer

puppeteer-canaryversionwithoutaxecorlatest.mov

playwright

playwright-canarywithoutaxecorelatest.mov

Environment:

Label	Value
Product	axe-core-npm
Version	4.7.4-f03670b.0
OS-Details	_MAC- Intel Core i7 - 11.6.8 & Windows11 _
BrowserDetails	Chrome Version 117.0.5938.88 (Official Build) (64-bit) & Firefox 117.0