Modernizing

[K20shores]

This PR is an attempt to modernize vextab

• Removed coffeescript with decaffeinate
• Replace webpack with vite
• Updates to the most recent version of vexflow
• Removed everything with eslint; there were like 30,000 errors and I didn't care to deal with that

When I have this completed, #106 will no longer be an issue.

I've resolved many issues, but I'm not completely done and have a few left. First off, all tests pass but the tests don't appear to catch every edge case.

I'm making this draft PR because I seem to have one last issue and I don't understand what is happening well enough to debug it. I know that it seems to be the multiStringTab test, but am unclear on what causes the rendering issue

It appears that some SVG element is created incorrectly and I don't quite understand how to debug this. To view this yourself

npm i
npm run test

and then check devtools

Other issues that I have not addressed but need to:

• [ ] lodash and qunit are both imported directly into the html files
  • lodash is there because I could not figure out how to get it to import in vextab.jison properly. But, I will either remove lodash entirely or figure out a better way to include it. Adding a script in tests.html allowed me to actually see the tests and start debugging differences between
  • qunit because it was already there, but I will also try to use an import in javascript instead when my remaining issues are done
• [ ] I have not tested the library build
• [ ] Add github actions to test, which I'll have to figure out how to run headless
• [ ] Get the playground working

I would appreciate any help in figuring out what is rendering incorrectly and why

[K20shores]

For more context, here's the published current version of vextab for the bass and 8-string:

and here is what my version is producing