Use fantasticon instead of gulp.

[lgarron]

Compared to our gulp pipeline, this is:

• Faster
• Much simpler
• Easier to maintain
• Not full of deprecated dependencies with vulnerabilities

This also changes the project organization to match other github.com/cubing projects more closely.

Closes:

• npm audit is failing #55
• Modernize the toolchain #93

[lgarron]

@jfly: This still needs a few fixups, and updates to the generated site. But it looks like this this will work. Any thoughts?

[jfly]

fantasticon looks like a good alternative for us!

Can we do one thing at a time? That is, can we do the biomejs stuff in a separate PR?

[lgarron]

Can we do one thing at a time? That is, can we do the biomejs stuff in a separate PR?

I don't feel comfortable introducing a new JS file without biome, but if you really want I could probably take it out.

[jfly]

I don't feel comfortable introducing a new JS file without biome

Could we add biomejs first, then?

[lgarron]

I don't feel comfortable introducing a new JS file without biome

Could we add biomejs first, then?

Not without applying it to the existing build script, which I'm not enthused about? But you seem to feel strongly about this, lemme find a way.

[lgarron]

I don't feel comfortable introducing a new JS file without biome

Could we add biomejs first, then?

Not without applying it to the existing build script, which I'm not enthused about? But you seem to feel strongly about this, lemme find a way.

I mean, I guess we could add biome scoped to scripts as a stub. That's a bit silly, but I guess it works.