Bump tracel-xtask from 2.2.1 to 4.1.3

[dependabot]

Bumps tracel-xtask from 2.2.1 to 4.1.3.

Release notes

Sourced from tracel-xtask's releases.

v4.1.3

• feat: add concept of dotenv families and add .infra and .infra.secrets. See documentation for more info.
• fix: make base_commands::secrets::env_file() function public

v4.1.2

• feat: new host subcommand for container command to connect to an host running the container
• feat: display elapsed time while rolling out containers

v4.1.1

• in secrets command we now try to edit secrets in pretty format when it's possible

v4.1.0

Breaking Changes

• The utils module aws_cli has been moved to aws::cli.

New features

• feat: add AWS naming.rs and regions.rs module that defines conventions for naming of AWS resources.

v4.0.1

• feat: add possiblity to transform an Environment<ExplicitIndex> into an Environment<ImplicitIndex>. Before, only the opposite operation was possible.

v4.0.0

Breaking Changes

• Initialization functions parse_args<C: clap::Subcommand>() and init_xtask<C: clap::Subcommand>() now return a tuple of arguments and environment. You must then use the returned environment from the tuple as environment and not the environment name contained in the arguments. You need to update the return type from init_xtask (and parse_args if you call it separately).

  Replace:

  let args = init_xtask::<Command>(parse_args::<Command>()?)?;

  With:

  let (args, environment) = init_xtask::<Command>(parse_args::<Command>()?)?;

• The container arguments have been updated and it is now possible to pass different values for promote_tag and rollback_tag.

New features

• feat: New global argument index which is the environment index. This makes now possible to support multiple staging or production environments. The Environment type is by default Environment<ImplicitIndex> which hides the index of the environment when this if the first one (index 1). The other type Environment<ExplicitIndex> always prints the environment index when displaying an environment.
• feat: container promote mechanism has been updated to replace latest tag with the environment name instead. Now it is possible to have a single container repository and promote a container to multiple environment at the same time.

Fixes

• fix: Remove annoying output when an .env files does not exist.

... (truncated)

Commits

• 8bce2e3 Bump version to 4.1.3
• 2f6a9fc fix: make env_file function in secrets public
• 5082327 feat: add concept of dotenv families, add .infra and .infra.secrets
• 7e12756 Bump version to 4.1.2
• 6dfb58a feat: add --user to container host command
• 9c9675a feat: create container host session with ubuntu user
• 69960ba feat: display elapased time while rolling out
• b2c9717 feat: new host subcommand for container command to connect to host
• df62b16 Bump verson to 4.1.1
• 5c07e50 feat: edit secrets in pretty format when possible
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[syl20bnr]

I'll handle this myself since there are breaking changes.

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.