Stop gitignoring most config.*.yaml, fixes #4893

[rfay]

The Issue

• config.*yaml files are gitignored, possibly breaking add-ons #4893

Most teams want config.*.yaml committed, and add-ons reinforce this.

How This PR Solves The Issue

Start gitignoring only config.local.yaml

Manual Testing Instructions

ddev config and ddev start a project. Get an add-on. git status should show config.*.yaml.

Release/Deployment Notes

This needs release note about the change.

[github-actions]

Download the artifacts for this pull request:

• all-ddev-executables.zip
• ddev-linux-amd64.zip
• ddev-linux-arm64.zip
• ddev-macos-amd64.zip
• ddev-macos-arm64.zip
• ddev-windows-amd64-installer.zip

See Testing a PR

[tyler36]

Fixes #4893 for me.

DDEV: ddev version v1.22.0-alpha2-65-g7a34932c

Test

1. Create new project.

   mkdir my-app
   cd my-app

2. Add version control.

   git init

3. Add DDEV to project.

   ddev config

4. Add addon with config

   ddev get ddev/ddev-selenium-standalone-chrome

5. Required addon files are available to commit.

   • ✅ .ddev/docker-compose.selenium-chrome.yaml
   • ✅ .ddev/config.selenium-standalone-chrome.yaml

[tyler36]

Thank you.

Adding config.local.yaml should also be really helpful for teams. I know I like to keep a static DB port for my "main" projects so I don't have to keep updating my database viewer config.

[gilbertsoft]

Looks good.

Just a note, I'm fine with the change. What about also ignoring config.override.yaml because it was suggested to use in the past? Would be less breaking.

[rfay]

@gilbertsoft I'd like people to completely forget about config.override.yaml, in fact, that feature should be removed now that we have actual overriding.