Add Addons:ApiView and AddonsApiViewUnlisted & rework AddonViewSet permissions

[eviljeff]

Fixes mozilla/addons#16318

Description

Replaces use of Addons:Review and Addons:ReviewUnlisted permissions in the API with dedicated Addons:ApiView and Addons:ApiViewUnlisted permissions, plus some refactoring to simplify the places we define permissions.

Context

Also replaces ReviewerTools:View and ReviewTools:ViewUnlisted too, but adds a migration so all existing groups containing those permissions get the dedicated replacements, so there's no breakage to Operations usage.

I took the opportunity to replace our custom AllOf and AnyOf classes with boolean logic, and break down our complex permission classes.

The issue asked for a single permission, but these permissions match our setup, and as users are added to groups that contain permissions, not assigned individual permissions, it doesn't make a difference.

Naming? Should they be Api:AddonView rather than Addons:ApiView? Some other naming?

Testing

• Run the migrations (happens automatically with make up
• Add yourself to a reviewer group that has Addons:Review in django admin/shell
  • that group should also have Addons:ApiView too from the migration
• verify you can access the detail page in local frontend for a non-public add-on
• check the /versions page too

Checklist

• Add #ISSUENUM at the top of your PR to an existing open issue in the mozilla/addons repository.
• Successfully verified the change locally.
• The change is covered by automated tests, or otherwise indicated why doing so is unnecessary/impossible.
• Add before and after screenshots (Only for changes that impact the UI).
• Add or update relevant docs reflecting the changes made.