Improve configuration management using Features

[quicksketch]

In last week's meeting, we reviewed Features module for D9/10+ and demonstrated how it can substantially improve the management of configuration in the Mukurtu installation profile. While Features has been substantially less used for deployment now that configuration management exists, the new version is excellent for managing installation profiles and separating config into different module: the common problem that we've been facing.

By switching our current custom modules into "features", we can more easily manage and export configuration into those modules.

• Part 1: Enable Features module Proof of Concept: Manage Module Configuration with Features #669
• Part 2: Rename profile to expected location for Features 672: Move mukurtu profile to expected location. #673
• Part 3: Fix installation profile to work with Features
• Part 4: Update each of the exported Features to be in a clean state 672: Refresh all exported config within Feature modules #674
• Part 5: Move configuration as needed to best location

[quicksketch]

While exporting features, I ran across a strange thing in exporting mukurtu_core module's search_api.server.mukurtu_solr_server.yml config file. There is an inline code comment:

dependencies:
  # Mukurtu devs, remember to delete config dependencies if you re-export.
  module:
    - search_api_solr

Which was helpful because when exporting the feature I noticed a lot of new dependencies being added:

I'm not sure why these dependencies are added or why they shouldn't be exported. I'll need to look into that a bit more deeply. For now I'm manually removing these dependencies as the code comment suggests.

[michael-wynne-wsu]

There's a chance that info is from @brian-wsu since he was doing solr config and testing (also could have been from Steve, but tagging Brian in case he knows!)

[quicksketch]

Thanks! I'm trying to figure out if there's a way we can permanently omit those dependencies. It's going to cause Features to think the feature needs to be exported if it doesn't match the current dependencies. And if we can eliminate one more manual process that will help maintenance.

[michael-wynne-wsu]

@quicksketch Have confirmed that this was not from @brian-wsu and was most likely from our previous lead dev. So I think you, @nick-deer, and @jonscottwsu can dig into it freely.