Re-add automatic NPM package updates once we have UI testing

[Piedone]

Is your feature request related to a problem? Please describe.

#16305 removes automatic NPM updates by Dependabot, since that didn't actually help us (#15694). However, in the long term, such automatic updates would still be useful.

Describe the solution you'd like

Re-add automatic NPM updates but only after we have an automatic way of verifying that no functionality is (badly) broken, i.e. revert #12834. Additionally, set NPM updates to happen once a week only, like we have it for NuGet packages.

Describe alternatives you've considered

Manually keeping those packages up-to-date, what we now do, and we did even when Dependabot was auto-updating (see again #15694).

[github-actions]

We triaged this issue and set the milestone according to the priority we think is appropriate (see the docs on how we triage and prioritize issues).

This indicates when the core team may start working on it. However, if you'd like to contribute, we'd warmly welcome you to do that anytime. See our guide on contributions here.

[github-actions]

We triaged this issue and set the milestone according to the priority we think is appropriate (see the docs on how we triage and prioritize issues).

This indicates when the core team may start working on it. However, if you'd like to contribute, we'd warmly welcome you to do that anytime. See our guide on contributions here.

[github-actions]

We triaged this issue and set the milestone according to the priority we think is appropriate (see the docs on how we triage and prioritize issues).

This indicates when the core team may start working on it. However, if you'd like to contribute, we'd warmly welcome you to do that anytime. See our guide on contributions here.

[MikeAlhayek]

@Piedone do we need to keep this tagged with 2.1? If this is not 2.1 critical, please change the milestone so we can ship 2.1 soon.

[github-actions]

We triaged this issue and set the milestone according to the priority we think is appropriate (see the docs on how we triage and prioritize issues).

This indicates when the core team may start working on it. However, if you'd like to contribute, we'd warmly welcome you to do that anytime. See our guide on contributions here.

[github-actions]

We triaged this issue and set the milestone according to the priority we think is appropriate (see the docs on how we triage and prioritize issues).

This indicates when the core team may start working on it. However, if you'd like to contribute, we'd warmly welcome you to do that anytime. See our guide on contributions here.