CV2-6604: Remove global keys permission

[melsawy]

Description

Check existing API keys and limit the usage of global keys.

• Log ApiKey last activity date
• Remove global API key permissions
• Verify that API key belongs to team
• Add rake task to set team_id for existing keys
• Add rake task to list global keys

References: CV2-6604

How to test?

• Re-run automated tests
• Using UI
• A) Generate API using workspace settings page(settings => Integrations => API Access)
• B) Generate API key using this guide
  For both cases I used graphql UI to run different quires

Checklist

• I have performed a self-review of my code and ensured that it is safe and runnable, that code coverage has not decreased, and that there are no new Code Climate issues. I have also followed Meedan's internal coding guidelines.

[caiosba]

Sawy, to be extra safe, I think we should make the team_id column on ApiKey mandatory. This should simplify the implementation since you won’t need to filter by non-null team IDs, and it also avoids the risk of forgetting to update that logic somewhere. Of course, you’ll need to run the rake task before deploying the code change; otherwise, the database migration will fail. Also, please rebase the PR since you already handled the last activity part in another PR.

[melsawy]

I think we should make the team_id column on ApiKey mandatory.

@caiosba for now I added a validation inside the model ApiKey so I can deploy and run the rake task and after deploying this PR I'll make the team_id column mandatory

[caiosba]

@melsawy , why not the opposite? A first PR with just the rake task, and then another PR that makes team_id mandatory?

[caiosba]

@melsawy what's the status here?

[melsawy]

@melsawy what's the status here?

Fixing tests (I have one test to fix) then run check-web tests

[caiosba]

@vasconsaurus would be good to get your eyes here too

[vasconsaurus]

@vasconsaurus would be good to get your eyes here too

I'll take a look now during my morning.

[vasconsaurus]

@melsawy, left a few questions just so I can better understand a few things. And one final question: are there any updates needed in the seeds script?

[melsawy]

are there any updates needed in the seeds script?

No @vasconsaurus

[vasconsaurus]

As always, thanks for the patience @melsawy.
Looks good to me once @caiosba requests are dealt with.

[caiosba]

@melsawy as we discussed, please keep the GraphQL field dynamic_annotation_field (here) but make it return nil. This way we don't break API clients, but also don't surface any data. I confirmed this is just used by the Slack Bot. Please also add a comment to flag that the GraphQL field is deprecated.

[melsawy]

@caiosba please review latest changes while I am fixing a flaky test.