Create initial contact form recipe

We're attempting to organize a team to work on this at Oomph. For me, I can help with gathering requirements and any design needs. Once we find the right person to lead, we'll send in the application!

There are a few things here which need to be changed.

I fixed the obvious things and left comments for a few others. Changing this to needs review for visibility, but I'm sure more work will follow.

Thank you for the very clear and sensible explanations! I think I can see a few ways forward; commented in the MR. Curious what you think.

I think this is ready to review again.

This issue has an MR needing review, so I guess it's...not a meta. Removing that designation.

That looks pretty good to me overall, just a few points of clarification/feedback/follow-ups.

Everything looks great here - I just have a suggestion for `drupal_cms_anti_spam` so that we can be certain the `authenticated` user role exists, without merely hoping that it was installed by the User module (even though it's a required role -- we're just being paranoid here).

Once that suggestion is implemented (or kicked back if it doesn't work), I'm okay committing this.

With regard to the anti spam integration of the contact form, please note there is a proposal at #3477309: Add the Friendly CAPTCHA module, and optional CAPTCHA support to the contact form to use friendlycaptcha for that. The contact form recipe requires the antispam recipe, so if the antispam changes strategy, this will change for the contact form as well.

Just wanted to leave this heads-up here just so that this recipe doesn't necessarily have to put extra effort into anti-spam, unless you have additional requirements?

I addressed all the feedback in the MR.
- I decided to list out all of the webform configuration instead of archiving the one form that shipped with Webform.
- I reverted any changes I made to the anti spam recipe. I'll create a followup issue to address changes in #3477309
- I did add a cypress e2e test, which passes locally, but not in CI. I don't think the E2E testing is configured quite right in the CI. It seems that the site is not getting installed in that CI environment.

This is shaping up; I love the test coverage! However, there are some flaws here that arise from a few minor misunderstandings of how to write recipes. I'm also very ambivalent about explicitly importing all of Webform's config entities, even the ones we don't need.

I believe I addressed everything. This is ready for another review.

Tests are failing, and we'll need to fix that before merging -- but I'm also busily building a basic framework for Cypress testing over in #3479610: Add Cypress test to the base SEO recipe, so let's postpone this on that.

Alright - #3479610: Add Cypress test to the base SEO recipe is in, so I think we can start hauling this to the finish line! Let's get the tests passing, and model the E2E tests on drupal_cms_seo_basic/tests/e2e/spec.cy.js.

I think this is good to go. The recipe looks good, is lean, and has strong test coverage (thanks @pfrilling)! We don't need to hold this up any longer. With regard to @jurgenhaas's point in #20, the tests will certainly help us adjust properly if and when we switch to Friendly CAPTCHA.

I'm shipping it!

Hmmm...something odd is going on with one test, not sure why - self-assigning to figure it out.

Boy, getting this to work properly took some doing, but it also revealed a major flaw in the way I built some of the Cypress infrastructure in #3479610: Add Cypress test to the base SEO recipe. What can I say...this whole thing is a learning experience. Anyway - that flaw, at least, is fixed and means that specs are properly isolated from each other.

Finally! The ship sails. Great work here!