[CI] Update Buildkite configuration for tags in main pipeline

[mrodm]

What is the problem this PR solves?

Restore buildkite settings to trigger builds on tags.
This are required to trigger the step:

fleet-server/.buildkite/pipeline.yml

Lines 207 to 215 in 6bee16f

	- label: ":jenkins: Release - Package Registry Distribution"
	key: "release-package-registry"
	trigger: "package-registry-release-package-registry-distribution"
	async: true
	build:
	branch: "main"
	meta_data:
	DOCKER_TAG: "${BUILDKITE_TAG}"
	if: "build.env('BUILDKITE_TAG') != ''"

How does this PR solve the problem?

// Explain HOW you solved the problem in your code. It is possible that during PR reviews this changes and then this section should be updated.

How to test this PR locally

Design Checklist

• I have ensured my design is stateless and will work when multiple fleet-server instances are behind a load balancer.
• I have or intend to scale test my changes, ensuring it will work reliably with 100K+ agents connected.
• I have included fail safe mechanisms to limit the load on fleet-server: rate limiting, circuit breakers, caching, load shedding, etc.

Checklist

• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files
• I have added tests that prove my fix is effective or that my feature works
• I have added an entry in ./changelog/fragments using the changelog tool

Related issues

• Follows ci: enable 9.* branches #4433

[v1v]

Thanks Mario, for explaining what's the purpose of those changes.

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
3 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarQube