Consider moving default config to a recipe

Problem/Motivation

When you enable lms_answer_plugins you also get default configuration enabled, however I think it is fairly unlikely that sites would want to use all of those activity types - they might want to pick or choose one or two activity plugins, or they might want to use different names (like 'essay' instead of 'free text') etc.

Also, shipped configuration in modules gradually goes out of date with core changes, so including the configuration is likely to increase the maintenance burden for the main module - we'll need to re-export config for minor and/or major core releases to keep up.

I think we could remove the configuration from the main module and do one of two things:

1. Move it as-is to a quickstart module - this would be the quickest solution since it'd just be a copy and paste.

2. Move it to a Drupal LMS quickstart recipe, this would be more work because recipes have a different structure, but eventually that could develop into becoming a Drupal LMS distribution or at least a set of recipes for different things.

I'm mostly concerned about the activity types here but it also applies to the blocks etc.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes