Create catalog-info file

[elastic-backstage-prod]

If you already have a ./catalog-info.yaml file defined in your repository, you probably want to close this PR.

If not - this PR provides you with the scaffolding for one. The catalog-info.yaml file is where you can define your infrastructure needs (such as Buildkite pipelines) in the form of Real Resource Entities.


If you already have a Buildkite pipeline defined in the elastic/ci repository, you can copy its definition in this catalog-info.yaml file (see instructions).

Once the pipeline definition is ingested into Backstage, Terrazzo will emit a warning about a duplicate definition with a warning similar to:
🙈 Ignoring remote manifest in favour of local one: buildkite.elastic.dev/v1=>Pipeline=> your-pipeline

At this point, it is safe for you to delete the Pipeline definition from the elastic/ci repository.

[cla-checker-service]

❌ Author of the following commits did not sign a Contributor Agreement:
15a8267

Please, read and sign the above mentioned agreement if you want to contribute to this project

[coolblknerd]

Hey, is there a way to override the failed CLA check? This PR was opened through Backstage automation and I'm trying to figure out how to work my way around this since this is becoming a consistent barrier.

[gigerdo]

@coolblknerd The problem is caused by the bot because it doesn't commit using an @elastic.co email. But it is possible to bypass branch protections and merge it anyway.

Alternatively if you recreate the commits under your own name it should pass the validation (However in that case you need to also set-up commit signing since that will be the next check that will fail).

[gigerdo]

Suggested change

	owner: group:control-plane-stateful-foundations
	owner: group:control-plane-stateful-applications

[gigerdo]

Suggested change

	github.com/team-slug: elastic/control-plane-stateful-foundations
	github.com/team-slug: elastic/control-plane-stateful-applications