Custom field with display

See merge request !6

# Conflicts:
#   web/modules/custom/thunderdome/config/install/thunderdome.settings.yml
#   web/modules/custom/thunderdome/config/schema/thunderdome.schema.yml

Custom plugin selector

See merge request !5

Custom field now accepts a parameter in display settings that will wrap the fields' content in a div of the class specified. The content is displayed in bullet form

Issue #11 Display setting added but not rendering on form, tried swapping for a select type field to no avail.

Issue #10 #12: Custom  field created. Able to add to content and outputs as expected. Field is wrapped in a div and assigned a place-holder class until display options integrated

Removed default build options in each animal controller as default is defined in one place under printDirections().

Issue #9: All paths routing and rendering instructions properly based on admin plugin selection at /admin/config/thunderdome

Issue #9: Conditional statements always result in rendering standard instructions instead of enhanced.

Issue #9: Sloth properly rendering based on admin input in config form. Implementing rest of the animals once I check current code base for quality.

Issue #9: Currently only have sloth integrated and trying to debug from there before moving on to other animal plugins. PluginNotFoundException: The Array plugin does not exist. Valid plugin IDs for Drupal\\AnimalPluginManager are: standard, enhanced

Issue #8: Created config variables for each animals plugin. Where I am planning to go from here is to inject the plugins into the ConfigForm but will check with mentor in the morning to ensure on the right path.

Issue #5 #6 #7: Animal plugin type defined and two new plugins created: Standard and Enhanced. Base class setup for example usage.

Issue #5 Basic structure in place with variables for animal type and instructions, as well as getter headers defined in the interface. Leaving issue open until I am sure those are all the members we need.

Issue #4 #3 Add node reference variable to module configuration

See merge request !4

Issue #3 Default node being instantiated and set properly in ThunderdomeConfigurationForm, all requirements met as outlined in MR and subsequent correspondence

Issue #4 #3 New features documented and configuration files set up properly in config/install and config/schema. Getting errors about calling member functions on null in ThunderdomeConfigurationForm

Issue #3 Twig template successfully renders any node reference in the thunderdome configuration form.

Entity reference variable accepted in module config form. Referenced node is rendered via twig template, only when manually enterred though. Passed variable appears to be null. Further testing needed

Custom events integrated. If use enters unexpected input on /delete/{id} form they are warned. If they try to delete thunderdome who knows...

Making progress. Custom event is created with listeners and logic, just have to continue testing the logic

Adding config form with checkbox and text input at /admin/config/thunderdome, just have to redirect and render form results