Relocate bundle specific translation permissions

Follow up for #1807776-109: Support both simple and editorial workflows for translating entities

Problem/Motivation

Moving the bundle specific C(R)UD permissions under the general translation section needs more thought.

Well, per-entity permissions are provided by the single entity-defining modules. To move them under the "Content translation" section we'd need to define some entity info keys ET could exploit to generate permission for each translatable entity. Then we would be back to a situation where you would have a mix of CUD permissions of different granularity under the same section (per-bundle node permissions, per-entity comment permissions and so on).

Proposed resolution

TBD.
A. Implement the keys and move them.
B. wont fix.
C. show them in both places, tagged with each section like #1868444: Introduce tags[] in module.info.yml file to categorize modules by provided functionality.
D. postpone this and open a much larger issue to rework the permissions page to be more like the modules page (with extra info collapsed, and maybe filers, sort, search and tags)

Remaining tasks

Discuss.

User interface changes

TBD. (new or changed features/functionality in the user interface, modules added or removed, changes to URL paths, changes to user interface text)

API changes

TBD. (API changes/additions that would affect module, install profile, and theme developers, including examples of before/after code if appropriate)