fix: collection level permissions - #2506

What does this PR do?

When using Document Level Permissions, we are supposed to ignore Collection Level Permissions and vice versa.

• Getting the Collection document is now always skipping authorization
  • will not throw a 404 anymore, but a 401
• fixed the returned sum on collection level permissions
• Fixed permission level for list, create, update and delete documents

Since this was discovered while I was working on Realtime, this PR also includes collection/document level permission for Realtime events:

• send the collection document as part of the event
• use collection permission or document permissions depending on the configured level

Test Plan

• extended tests for the Database
• added realtime tests

Have you read the Contributing Guidelines on issues?

✅