[WIP] Move to Mocha tests

[harryadel]

• Fix failing server side tests

• Fix linting

• Verify .find hooks work
  History & README were updated to properly reflect the current package status

• Support both sync and async operations in all hooks
  As I was working on the package I thought it'd be possible to support async operations in sync hooks but I then figured how hard it'd be to support such a thing as blocking sync execution based on a sync operation wouldn't be feasible and allowing async operations as fire-and-forget to not block things would be awkward. I know understand why @bhunjadi decided to drop sync support and now hooks are only triggered on async operations (ex: findOneAsync instead of findOne)

   collection.before.findOne(async function(userId, selector) {
     console.log('Async hook started')
     await fetch('/api/log-access') // Takes 200ms
     console.log('Async hook finished')
   })
  
   // Sync call
   const doc = collection.findOne({name: 'John'})
   console.log('findOne returned:', doc)

   Async hook started                    // ← Hook fires immediately
   findOne returned: {_id: 1, name: 'John'}  // ← findOne completes WITHOUT waiting
   Async hook finished                   // ← Hook completes later (200ms later)

• Fix CI tests

• Utilize https://packosphere.com/lai/collection-extensions until Integrate lai:collection-extensions into core meteor/meteor#13830 gets merged

• Review files one last time compared to their older versions to ensure they still retain the same structure

• Try it out in my top secret project @DanielDornhardt

• Once it's ready, ping @vparpoil for one last test

• Profit??

---

Post release

• Update other packages that rely on it like https://github.com/cult-of-coders/grapher
• Partitioner [WIP] 3.0 migration meteor-partitioner#38

To fix the issue, we will add a permissions block at the root of the workflow. This block will apply to all jobs in the workflow unless overridden by a job-specific permissions block. Since the workflow only needs to read repository contents (e.g., for checking out code), we will set contents: read as the minimal required permission.

---