Restructure chef specs to match code structure

What does this MR do?

Restructure the chef related specs to match the code structure.

The new structure is as below

$ tree -L 3 spec/chef

spec/chef
├── cookbooks
│   ├── consul
│   │   ├── libraries
│   │   ├── recipes
│   │   └── resources
│   ├── crond
│   │   ├── recipes
│   │   └── resources
│   ├── gitaly
│   │   ├── libraries
│   │   └── recipes
│   ├── gitlab
│   │   ├── libraries
│   │   ├── recipes
│   │   └── resources
│   ├── gitlab-ee
│   │   ├── libraries
│   │   ├── recipes
│   │   └── resources
│   ├── gitlab-kas
│   │   └── recipes
│   ├── gitlab-pages
│   │   └── recipes
│   ├── letsencrypt
│   │   ├── libraries
│   │   ├── recipes
│   │   └── resources
│   ├── logrotate
│   │   └── recipes
│   ├── mattermost
│   │   └── recipes
│   ├── monitoring
│   │   ├── libraries
│   │   └── recipes
│   ├── package
│   │   ├── libraries
│   │   ├── recipes
│   │   └── resources
│   ├── patroni
│   │   ├── libraries
│   │   └── recipes
│   ├── pgbouncer
│   │   ├── libraries
│   │   └── recipes
│   ├── postgresql
│   │   ├── recipes
│   │   └── resources
│   ├── praefect
│   │   └── recipes
│   ├── redis
│   │   └── recipes
│   ├── registry
│   │   └── recipes
│   └── spamcheck
│       └── recipes
├── fixtures
│   ├── cookbooks
│   │   ├── acme
│   │   ├── test_consul
│   │   ├── test_crond
│   │   ├── test_gitlab
│   │   ├── test_gitlab_ee
│   │   ├── test_package
│   │   └── test_postgresql
│   ├── fauxhai
│   │   └── ubuntu
│   └── migration
│       ├── failed-migration-status-file
│       └── successful-migration-status-file
├── gitlab-ctl-commands
│   ├── gitlab_ctl_spec.rb
│   └── lib
│       ├── gitlab_ctl_backup_spec.rb
│       ├── gitlab_ctl_pg_upgrade_spec.rb
│       ├── postgresql
│       ├── postgresql_spec.rb
│       ├── praefect_spec.rb
│       ├── upgrade_check_spec.rb
│       └── util_spec.rb
├── gitlab-ctl-commands-ee
│   ├── geo_replication_spec.rb
│   ├── geo_spec.rb
│   ├── lib
│   │   ├── consul_spec.rb
│   │   ├── geo
│   │   ├── patroni_spec.rb
│   │   ├── pgbouncer_spec.rb
│   │   └── postgresql
│   ├── promote_db_spec.rb
│   ├── promote_to_primary_node_spec.rb
│   ├── promotion_preflight_checks_spec.rb
│   └── replicate_geo_database_spec.rb
└── support
    ├── shared_context
    │   ├── ctl_shared_context.rb
    │   ├── gitlab_rails_shared_context.rb
    │   └── object_store_shared_context.rb
    └── shared_examples
        ├── consul_service_name.rb
        ├── geo_promotion_command_accepts_option_shared_examples.rb
        ├── gitlab_geo_promotion_commands_shared_examples.rb
        ├── gitlab_yml_object_storage_shared_examples.rb
        ├── logrotate_config.rb
        ├── registry_service.rb
        ├── runit_service.rb
        └── yaml_check.rb

77 directories, 29 files

Related issues

Related to #6721 (closed)

Checklist

See Definition of done.

For anything in this list which will not be completed, please provide a reason in the MR discussion

Required

• Merge Request Title, and Description are up to date, accurate, and descriptive
• MR targeting the appropriate branch
• MR has a green pipeline on GitLab.com
• Pipeline is green on dev.gitlab.org if the change is touching anything besides documentation or internal cookbooks
• trigger-package has a green pipeline running against latest commit

Expected (please provide an explanation if not completing)

• Test plan indicating conditions for success has been posted and passes
• Documentation created/updated
• Tests added
• Integration tests added to GitLab QA
• Equivalent MR/issue for the GitLab Chart opened