CP: ci.yaml changes for packaging (#117133)

[syedsoban0099]

• Migrate Packaging Builders to .ci.yaml (Migrate Packaging Builders to .ci.yaml #115569)

• packaging builder initial config

• add release scheduler parameter

• remove stables

• add taskname + test owner

• testowner test

• comment structure

• test naming convention

• test adding tags

• add timeout

• prune names

• Update testowners.

• Move packaging to shards section.

• Set packaging as shard.

• Use packaging V2

Co-authored-by: godofredoc godofredoc@google.com

• Revert deleted line.

• use deploy suffix (Use Deploy Suffix #116533)

• Update docs_deploy builder with the real name. (Update docs_deploy builder with the real name. #116631)

This is removing the temporary comments and simplifying the name.

Bug: #115489

• Add Remaining Packaging Builders (Add Remaining Packaging Builders #116683)

• add stable packaging builders

• update testowners

• consolidate and use enabled_branches

• update to reflect the consolidation

• Several fixes to packaging builders. (Several fixes to packaging builders. #116800)

It includes the following changes:

• Adds main as the enabled branches.
• Adds docs_beta and docs_stable to pass the expected gcp project.
• Adds dimensions to packaging arm64 to ensure that it runs on arm64
  bot.

Bug: https://github.com/orgs/flutter/projects/43

• Pass drone_dimensions as part of the main target. (Pass drone_dimensions as part of the main target. #116812)

• Pass drone_dimensions as part of the main target.

Drone dimensions were passed as properties when the sharding utility is
expecting them in the target.

Bug: #116794

• Use dimensions instead of drone_dimensions.

• Use a map format.

Co-authored-by: sealesj 103135467+sealesj@users.noreply.github.com

Replace this paragraph with a description of what this PR is changing or adding, and why. Consider including before/after screenshots.

List which issues are fixed by this PR. You must list at least one issue.

If you had to change anything in the flutter/tests repo, include a link to the migration guide as per the breaking change policy.

Pre-launch Checklist

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
• I read the Tree Hygiene wiki page, which explains my responsibilities.
• I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
• I signed the CLA.
• I listed at least one issue that this PR fixes in the description above.
• I updated/added relevant documentation (doc comments with ///).
• I added new tests to check the change I am making, or this PR is test-exempt.
• All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[CaseyHillers]

This PR looks like it was branched off of a different branch from master, resulting in a large diff and meaning it will not be mergeable. Please see tree hygiene for more details about how to open pull requests to Flutter repositories.

Feel free to create a new pull request with these same changes branched off of master, and thanks for contributing!