Convert web tests to browser tests for content_moderation module

I have fixed all but one of the failing tests. I believe the failing test is evidence that there is a bug in core. The test passed in simpletest because it was checking for text by doing a case sensitive search:

// \Drupal\Tests\content_moderation\Functional\ModerationStateNodeTypeTest::testEnablingOnExistingContent
$this->assertNoRaw('Save and publish');

The above assertion is failing because the raw text "Save and Publish" is found as assertNoRaw is case insensitive with BrowserTestBase.

I will create a separate issue and amend the test so that we can prove it is broken. I will relate that test to this one once it is created.

I'm going to wait for feedback on #2864060: ModerationStateNodeTypeTest::testEnablingOnExistingContent assertion is misleading and if there is a quick resolution there then I will pick this up again and try and push for a complete conversion of simpletests. Otherwise I will remove the \Drupal\content_moderation\Tests\ModerationStateNodeTypeTest conversion so we can get some of the conversions through and then create a followup issue for #2864060: ModerationStateNodeTypeTest::testEnablingOnExistingContent assertion is misleading

It appears that the intent of the test was to do a case sensitive check. See: #2864060-5: ModerationStateNodeTypeTest::testEnablingOnExistingContent assertion is misleading.

"Save and publish" is the button text when content moderation isn't installed and "Save and Publish" is the button text once it is installed, so I think this is correct.

We should supply a patch that performs a case sensitive check for the test "Save and publish"

It's my view that neither issue need hold up the other. If #2864060: ModerationStateNodeTypeTest::testEnablingOnExistingContent assertion is misleading gets committed first we can reroll and refactor this patch and vice versa.

This patch provides the same level of coverage as is in core currently.

But let's hope #2864060: ModerationStateNodeTypeTest::testEnablingOnExistingContent assertion is misleading gets committed soon and we don't even need to think about it :)

Duplicate of last message. Not sure how to delete.

Now that #2864060: ModerationStateNodeTypeTest::testEnablingOnExistingContent assertion is misleading has been committed, this patch required a re-roll.