feat: Add community metadata validation

[leblowl]

Pull Request Checklist

• I have linked this PR to related GitHub issue.
• I have updated the CHANGELOG.md file with relevant changes (the file is located at the root of monorepo).

(Optional) Mobile checklist

Please ensure you completed the following checks if you did any changes to the mobile package:

• I have run e2e tests for mobile
• I have updated base screenshots for visual regression tests

[leblowl]

I'm still adding some tests, but I think this is ready for another look. Thanks!

[Kacper-RF]

Please merge newest develop in Your branch and resolve conflicts in state manager.
Also there is problem in e2e invitation link test.

[siepra]

I'd gone through all the changes and paid extra attention to the parts I'm confident with, although the size of this PR makes it hard to be fully accurate so there's a great chance I missed something. I think I'd be best if you also get approval from someone else.

I see there're still some conflicts and failing e2e tests but overall it looks fine.

[siepra]

It's impossible as a factory for mocking data accepts certificate as null/undefined on purpose to perform some more advanced combinations, eg. mocking it automatically or storing and invalid redux entry basing on it's value. I think the best way is to just use // @ts-expect-error knowing it's just a matter of mocking test data

[leblowl]

@EmiM Do you think the e2e tests are failing because of changes in this PR? It also looks like a backend with tor test is failing.

[EmiM]

@EmiM Do you think the e2e tests are failing because of changes in this PR? It also looks like a backend with tor test is failing.

Yes but because of not compatible arguments after adding orbitdb key. Look at 'Guest clicks invitation link with invalid invitation code'. This test is skipped anyway so you can either add lacking argument or remove both 'Guest clicks invitation link with invalid invitation code' and 'Guest sees modal with warning about invalid code, closes it'

Do backend tor tests pass on your local machine? If not then it may be because of this PRs changes.

[EmiM]

I think this can be merged when e2e tests will pass

[leblowl]

@EmiM Do you think the e2e tests are failing because of changes in this PR? It also looks like a backend with tor test is failing.

Yes but because of not compatible arguments after adding orbitdb key. Look at 'Guest clicks invitation link with invalid invitation code'. This test is skipped anyway so you can either add lacking argument or remove both 'Guest clicks invitation link with invalid invitation code' and 'Guest sees modal with warning about invalid code, closes it'

Do backend tor tests pass on your local machine? If not then it may be because of this PRs changes.

When I run the tor tests locally, I get the following error:

@quiet/backend:   ● Connections manager › dials many peers on start
@quiet/backend:     thrown: "Exceeded timeout of 100000 ms for a hookfalse.
@quiet/backend:     Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."

[leblowl]

Apparently, I am having trouble running Tor via those tests:

symbol lookup error: undefined symbol: evutil_secure_rng_add_bytes