chore(deps): bump arduino/setup-task from 1 to 2

[dependabot]

Bumps arduino/setup-task from 1 to 2.

Release notes

Sourced from arduino/setup-task's releases.

2.0.0

Migration Guide

The version of the Node.js runtime used to execute the action has been updated from 16 to 20. This could be a breaking change for certain GitHub Actions workflows.

If a workflow with dependency on the arduino/setup-task action uses only GitHub-hosted GitHub Actions runners, no changes are required.

If the workflow uses a self-hosted runner, the workflow run might fail after updating arduino/setup-task:

Error: System.ArgumentOutOfRangeException: Specified argument was out of the range of valid values. (Parameter ''using: node20' is not supported, use 'docker', 'node12' or 'node16' instead.')
   at GitHub.Runner.Worker.ActionManifestManager.ConvertRuns(IExecutionContext executionContext, TemplateContext templateContext, TemplateToken inputsToken, String fileRelativePath, MappingToken outputs)
   at GitHub.Runner.Worker.ActionManifestManager.Load(IExecutionContext executionContext, String manifestFile)
Error: Fail to load arduino/setup-task/v2/action.yml

This means an older runner version that does not provide Node.js 20.x is installed on the runner machine and you must update the runner version.

Changelog

Breaking

• Update Node.js runtime for action from 16 to 20 (#919)

Enhancement

• Various dependency updates

Full Changeset

arduino/setup-task@1.0.3...2.0.0

Contributors

• @​gdraynz

1.0.3

Changelog

Enhancement

• Add support for all Task build architectures (43e1bb8c37ce39c24e88b4622c2f66b6d7d9ebbd)

Full Changeset

arduino/setup-task@1.0.2...1.0.3

1.0.2

Release Notes

... (truncated)

Commits

• b91d5d2 update readme (#929)
• f2514b0 Bump node from 16 to 20 (#919)
• 2007903 Merge pull request #928 from arduino/dependabot/npm_and_yarn/prettier-3.2.5
• 3f2ef95 build(deps-dev): bump prettier from 3.2.2 to 3.2.5
• 88d658b Merge pull request #927 from arduino/dependabot/npm_and_yarn/types/node-16.18.79
• b79a1c3 build(deps-dev): bump @​types/node from 16.18.78 to 16.18.79
• 5abddba Merge pull request #926 from arduino/dependabot/npm_and_yarn/types/node-16.18.78
• b3e99c0 build(deps-dev): bump @​types/node from 16.18.76 to 16.18.78
• 4145542 Merge pull request #924 from arduino/dependabot/npm_and_yarn/typescript-eslin...
• 10406e6 build(deps-dev): bump @​typescript-eslint/parser from 6.19.1 to 6.20.0
• 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 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)

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[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.