Reduce onboarding complexity by replacing dependency on yarn about accessibility-insights-action

[dbjorge]

I'm moving this from "await community interest" back to "ready for triage" based on several recent support threads that were challenging to debug which occurred because of this issue. Besides increasing the amount of steps required to onboard, it makes it easy to introduce very confusing issues - for example, mis-ordering a yarn install vs node install step can cause different parts of the task to end up using different node versions in ways that aren't obvious.

This issue has been marked as ready for team triage; we will triage it in our weekly review and update the issue. Thank you for contributing to Accessibility Insights!

[asksep]

We split this into 2 issues to track adding documentation as an initial 'go-do' task Add the yarn tooling requirement to our documentation (easy to do) #1123.

Second, we flagged this original thread as "await community interest" to track if this yarn-dependency is prevalent across other teams trying to onboard.

[microsoft-github-policy-service]

This issue has been marked as ready for team triage; we will triage it in our weekly review and update the issue. Thank you for contributing to Accessibility Insights!

[katydecorah]

To add another observation, windows-latest and ubuntu-latest are now on Node v18. This means we have also seen more users needing to add the NodeTool step to target Node 16. Since Node often comes packaged with npm, I'm curious if the option to switch from yarn to node would help reduce onboarding complexity.

[microsoft-github-policy-service]

This issue has been marked as ready for team triage; we will triage it in our weekly review and update the issue. Thank you for contributing to Accessibility Insights!