APERTA-12445 first card

[benjaminkreen]

JIRA issue: https://jira.plos.org/jira/browse/APERTA-12445

What this PR does:

We seem to be lacking the :view_participants and :manage_participant permissions for migrated cards, and in the custom card configurator view. I'm attempting to add those. Here's the chart i've created to use as a key: https://docs.google.com/spreadsheets/d/1TOAN0RITgLLM6f-6zCEu3FM0HdFe5AvCSx2wmYlBY3M/edit?usp=sharing

Special instructions for Review or PO:

All sorts of fun! Once card config is enabled, you can toggle these settings to your heart's desire. To update existing cards, we're going to need to go into the UI and update them individually, unless there's some more cleverer way to do that.

Major UI changes

TWO NEW COLUMNS!

Code Review Tasks:

Author tasks (delete tasks that don't apply to your PR, this list should be finished before code review):

• If I made any UI changes at all, I've let the entire QA team know in the JIRA ticket and in the Aperta QA hipchat room.

• I have set the correct component(s) in the JIRA ticket

• I have set an appropriate resolution in the JIRA ticket

• I have ensured that the Heroku Review App has successfully deployed and is ready for PO UAT.

Reviewer tasks (these should be checked or somehow noted before passing on to PO):

• I read through the JIRA ticket's AC before doing the rest of the review
• I ran the code (in the review environment or locally). I agree the running code fulfills the Acceptance Criteria as stated on the JIRA ticket
• I read the code; it looks good
• I have found the tests to be sufficient for both positive and negative test cases

[benjaminkreen]

Let me know if I should test the toggle permission functionality too