Ensure ManageFieldsLifecycleTest::testCrudFields() test coverage is covered by ManageFieldsTest then delete it

Problem/Motivation

ManageFieldsUiTest was added in 2009(!) it has not dramatically changed.

Since it was added, we added FieldUiDeleteTest in 2015 in #2575605: Field delete form does not display configuration dependencies that will be updated/deleted → which has comprehensive coverage for field deletion, and also doesn't depend on taxonomy or node modules.

Also testCrudFields() is mostly duplicated by the much more modern ManageFieldsTest, which uses entity_test module instead of article/basic page/tags fields etc.

We should check for coverage in testCrudFields() that's not in ManageFieldsTests or other field_ui tests, add anything over that makes sense, then delete it to reduce the duplication.

Steps to reproduce

Proposed resolution

Remove the two test methods from ManageFieldsUiTest and leave the more comprehensive coverage in FieldUiDeleteTest.

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet