Entity operations to field UI shown in config overview

Attached patch reorders them, so "Translate" is the first one (and default) if it exists.
I'm wondering anyway if we should remove the others, as we don't want users to lose focus of what are they doing at the moment.

Can we remove the rest of the items instead? We worked pretty hard to remove them and this appears because it alters them in... Not good IMHO :/ Its confusing because other things don't have their other operations.

If there is a translate operation, remove the others.

Tested this manually. Looks good.

Needs tests. Updated issue summary. I don't think this needs usability review, it does what the rest of these screens do.

BTW also found #2506793: Config translation shows search field below table while reviewing this. Should be easy to fix I hope :)

We already have code to do this, but it operates too early so that the dynamic operations from field UI are still added afterwards. See attached patch.

Ahh ConigTranslationOverviewTest doesn't enable field_ui module, that's why the test-only patch doesn't fail. Not sure whether we want to accept the performance cost of enabling it, just for this test. Hmm...

That test already enables views_ui... I don't think is such an impact.

Yeah I an not concerned of needing to enable field_ui :)

So I was wrong: just enabling field_ui doesn't cut it, because the config_test entity type does not have the bundle_of property.

So in order to properly test this, I added a entity_test_operation module that provides a test entity operation unconditionally. In order do that I also had to fix the API documentation.

This time the test-only patch should actually fail.

Looks good except:

1. +++ b/core/modules/config_translation/src/Tests/ConfigTranslationOverviewTest.php
   @@ -86,6 +103,15 @@ public function testMapperListPage() {
   +      // Make sure there is only a single 'Translate' operation for each
   +      // dropbutton, either.
   

   Either?

2. +++ b/core/modules/system/tests/modules/entity_test_operation/entity_test_operation.info.yml
   @@ -0,0 +1,6 @@
   +name: 'Entity Operation Test'
   +type: module
   +description: 'Provides a test operation to entities.'
   +package: Testing
   +version: VERSION
   +core: 8.x
   

   Should be hidden: true, no?

1. Ahhh I had seen that and then forgot. You eagle-eye! ;-P Will fix later

2. Our test modules no longer have hidden: true because they are not discovered anyway, unless you set $settings['extension_discovery_scan_tests'] = TRUE; explicitly in which case it's useful if they show up in the UI (we then collapse the Testing details element by default so it's not such a nuisance). So that should be fine.

Here we go.

Yay, thanks! I grepped for hidden: true in test modules, and we still have that around quite a bit, but the reason I needed to grep in the first place was I was unsure :D

Fails seem to be unrelated:

Segmentation fault
FATAL Drupal\views\Tests\RenderCacheIntegrationTest: test runner returned a non-zero error code (139).

Nice test coverage and docs improvements. This issue addresses a normal bug and is allowed per https://www.drupal.org/core/beta-changes. Committed 88a73d8 and pushed to 8.0.x. Thanks!

Superb, thanks!