feat: add deprecation warnings to access commands

[wraithgar]

npm/statusboard#500

[npm-cli-bot]

no statistically significant performance changes detected

timing results

app-large	clean	lock-only	cache-only	cache-only peer-deps	modules-only	no-lock	no-cache	no-modules	no-clean	no-clean audit
npm@8	42.248 ±0.30	17.747 ±0.14	15.643 ±0.00	19.172 ±1.72	2.743 ±0.00	2.755 ±0.01	2.251 ±0.04	10.984 ±0.10	2.217 ±0.01	3.182 ±0.13
#5347	40.851 ±3.65	17.734 ±0.10	15.806 ±0.19	18.060 ±0.84	2.664 ±0.01	2.764 ±0.04	2.251 ±0.01	10.819 ±0.05	2.234 ±0.01	3.339 ±0.09

app-medium	clean	lock-only	cache-only	cache-only peer-deps	modules-only	no-lock	no-cache	no-modules	no-clean	no-clean audit
npm@8	30.285 ±1.01	13.456 ±0.02	11.635 ±0.36	12.798 ±0.96	2.516 ±0.01	2.552 ±0.02	2.198 ±0.01	7.961 ±0.11	2.158 ±0.01	2.841 ±0.02
#5347	29.753 ±1.42	13.315 ±0.12	11.945 ±0.15	12.831 ±0.07	2.537 ±0.02	2.537 ±0.01	2.234 ±0.01	7.924 ±0.03	2.137 ±0.01	2.913 ±0.03

[darcyclarke]

Just want to block this for now until we've had a discussion about whether npm/statusboard#477 can land prior to v9. If not, then we should likely hold on removing these commands for another major cycle (which would be crappy) but the timeframe may be tight 🤷🏼‍♂️ let's chat today about it.