feat: Update example to Parse Server 8

[dblythy]

Closes: #558
Closes: #398
Closes: #396
Closes: #399

[parse-github-assistant]

I will reformat the title to use the proper commit message syntax.

[parse-github-assistant]

Thanks for opening this pull request!

[mtrezza]

Which issue does this PR close? Is it #558?

[dblythy]

Yes sorry

[dblythy]

Some QOL improvements here:

• using ESM
• using the JS SDK in the demo file
• presenting an opinionated folder structure and class design that should allow for better testability
• adding unit tests that can run very fast and in parallel
• simplification of the CI - no need to have multiple node versions

[mtrezza]

Great work, just about these:

• presenting an opinionated folder structure and class design that should allow for better testability
• adding unit tests that can run very fast and in parallel

I appreciate the approach to apply a theoretical best-practice, but for this simple repo it seems a bit much. We want to keep this repo as slim as possible to demo Parse Server in a light weight, few dependencies, low maintenance repo.

Parallel testing, new test framework with jest, etc. are out of scope; we want to avoid that at some point in the future we have to spend time fixing this, as it's not the purpose of this repo. Could you please keep the structure and nomenclature we are currently using across most repos (/spec) and remove the subfolders "Hello", etc. Just a test file with the same name as the file that is being tested should provide enough overview, e.g. /spec/TestObject.spec.js.