Move configuration defaults from .config files to classes

[emmberk]

Description

• Classes will be created in a valid state instead of initializing before setting required properties. These classes will also be able to be unit tested in their valid/default state.
• Features will no longer need to drop .config files, reducing the total number of .config files and simplifying feature definitions. These .config files also cause default configurations to appear as custom configurations in the Admin Console:
  
• Downstream projects can drop .config files containing only the properties that are different from the defaults defined in DDF.

Expected behavior:

• Dropping a .config file that contains not all of the properties for a config should successfully update the properties but keep the defaults for all not-included properties.
• Configurations appear to set to the defaults in the Admin Console:
  

Version

2.14.0

Additional Information

none

[emmberk]

ConfigurationApplication still needs to have the default sets when the class is instantiated.

[emmberk]

This is still relevant.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs within 7 days. Thank you for your contributions.