Don't query ObjectPermission table when user has access_all_objects capability

[Repumba]

Your checklist for this pull request

• I've read the contributing guideline.
• I've tested my changes by building and running the project, and testing changed functionality (if applicable)
• I've added automated tests for my change (if applicable, optional)
• I've updated documentation to reflect my change (if applicable)

What is the current behaviour?

When new sample is added, we add new entry in ObjectPermission table for every user with access_all_objects capability
This causes that we have many unnecessary rows in this table and MWDB works slower
Additionally, it's harder to revoke access to objects, when user loses the access_all_objects capability

What is the new behaviour?

Instead of adding new rows in ObjectPermission, check if user has access_all_objects capability when querying
When user loses access_all_objects capability, they lose access to them (applies only in cases, when access to object is granted only by this capability)

Test plan

Under development

Closing issues

closes #758

[Repumba]

This branch cannot pass tests due to a problem with karton-mwdb-reporter
I have to wait for CERT-Polska/karton-mwdb-reporter#30

[psrok1]

Looks great! I've added migration and bumped Karton services