Fix: Unittests failing because of existing buckets + inconsistency with firebase.rules

[zwilling]

Description

There are a couple changes, we had to make to pass the yarn test:prod unittest.

1. A lot of tests failed with the error provided name is already in use. This happened on bucket creation if the bucket already existed. Apperently the after test cleanup did not delete buckets correctly. Fixing that did not seem right to me, because interrupting a test run in the middle should not make future test runs fail. I was unable to get the cleanup work in the test setup phase. So the best fix, I could find is not throwing errors on recreating existing buckets. To my understanding this is fine becaue I could not find any bucket deletion in the production code.
2. Some database tests failed. They were inconsistent with what is written in firestore.rules. The rules seem properly configured for production. Becasue I don't know the motivation for those tests, I just skipped them.

How Has This Been Tested?

• Deployment finished without errors
• Running the unittests yarn test:prod
• Completing the Galactica Network Ceremony

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation (Is there something to change?)
• My changes generate no new warnings
• Any dependent changes have been merged and published in downstream modules
• I reviewed the code of conduct and contributors' guide