The "yq" tool dependency is managed via the Go modules system. It must be invoked via `go tool` in order for the managedversion to be used.

The "Task" task runner tool is used to perform all common development and maintenance operations for the project.Previously, the version of Task was not well managed.The GitHub Actions workflows used the latest version of Task, only constrained by major version. This meant that theGitHub Actions workflows could break at any time through a new release of Task that contained regressions or breakingchanges.The contributors used whichever version of Task happened to be installed on their machine. This meant that they mightget different results from that produced by the environment of the GitHub Actions workflows.The better solution is to take the same approach for managing the Task dependency as is done for the project's otherdependencies:* Install a specific version of Task according to a single source of versioning data.* Use the Dependabot service to get automated update pull requests.Since Task is a Go module-based project, this can be accomplished by using the Go modules system, which has explicitsupport for tool dependencies as of the Go 1.24 release.