Prune Grunt tasks

[samreid]

Discovered in #1459, there are many tasks in chipper's Gruntfile.js or perennial's Gruntfile.js that:

• appear unused
• are unrelated to the other grunt responsibilities

@zepumph and I recommend reviewing each grunt task to see if it can be deleted or moved to a separately executable script. Things that should remain are: simulation lifecycle events like grunt --brands=phet grunt dev grunt rc grunt lint and their dependencies. And for tasks that must remain stable, well-supported, and backward-compatible for maintenance tasks.

This work will help us modularize & limit our usage of grunt, which we would like to "abandon" #1436

It will also free us up to use other runtimes (such as deno or tsx) or TypeScript as desired.

I will tag suspicious grunt tasks, then bring to Monday's developer meeting. I will make annotations in perennial/main and chipper's typescript_chipper_1459_b branch. (and they can (mostly?) be seen below)

[zepumph]

Much of this issue should probably wait until we finish discussing phetsims/perennial#370.