Bumps [@actions/core](https://github.com/actions/toolkit/tree/HEAD/packages/core) from 1.11.0 to 1.11.1.- [Changelog](https://github.com/actions/toolkit/blob/main/packages/core/RELEASES.md)- [Commits](https://github.com/actions/toolkit/commits/HEAD/packages/core)---updated-dependencies:- dependency-name: "@actions/core"  dependency-type: direct:production  update-type: version-update:semver-patch...Signed-off-by: dependabot[bot] <support@github.com>

GitHub downloads each action run in a workflow during runtime and executes it as a complete package of code before youcan use workflow commands like run to interact with the runner machine. This means that we must provide all JavaScriptpackage dependencies as part of the distributed action in order for it to be usable in workflows.A naive approach to doing this is checking in the `node_modules` folder. However, this approach results in a huge amountof frequently changing external content being included in the repository, much of which is not even part of the executedprogram.A far better approach is to use the excellent ncc tool to compile the program, including all the relevant code from thedependencies, into a single file.We use a "continuous packaging" approach, where the packaged action code that is generated via ncc is always kept insync with the development source code and dependencies. This allows a beta version of the action to be easily used inworkflows by beta testers or those who need changes not in the release simply by using the name of the branch as theaction ref (e.g., `uses: arduino/arduino-lint-action@main` will cause the version of the action from the tip of the`main` branch to be used by the workflow run).The update of the package dependency results in a change to the packaged code, so the packaging is here updatedaccordingly.