Switch to using AutoUpdate's approach to running core checks

Woo! Linting & testing back up and working.

I introduced this alternative approach for Package Manager/Automatic Updates in 📌 Stop reusing core's commit-code-check.sh in favor of 4 simple commands Fixed . But there's one important difference between the two projects: PM/AU does not contain any JS, but PB does!

So right now you lost all JS code quality checks 😅 You'll want to port those over.

Good point @Wim Leers!

But I think we only have one non-Svelte JS file, and we were already going out of our way to disable JS checks for those, since they contain HTML and CSS as well.

That's why our version committed above has an additional step to run our lint:svelte command

I'll leave this for @chrisfromredfin to ponder, but I think we're okay here

As I've thought about this, it feels the same as the yaml linter. We could do it now or do it later, but the consequence regardless is minimal. If we discover it late, it's maybe 30 minutes to fix both, because the surface area is so small. It might be nice to open a lower-priority ticket to add those two things.

My larger concern is that the javascript that IS inside of .svelte files is passing Drupal JS checks, and I'm hoping lint:svelte is able to check those things.

Documenting here that yes, lint:svelte does check for proper formatting inside of the .svelte files, so I do think we're good here.