Remove hardcoded version from workflow

[kin0992]

List of changes

• Enable corepack
• Use turbo on major version 2

Motivation and context

We want to use the latest turbo version in our workflows.

Type of changes

• Add new resources
• Update configuration to existing resources
• Remove existing resources

Does this introduce a change to production resources with possible user impact?

• Yes, users may be impacted applying this change
• No

It can impact those projects that are pointing to main when referencing the updated workflow.

Other information

There is a PR that shows how to migrate from turbo 1 to version 2.
Reference: pagopa/trial-system#267

Migration guide

First, check the official documentation for any doubts.

• Run yarn dlx @turbo/codemod migrate or npx @turbo/codemod migrate (official tool that should help to migrate. Follow the wizard)
  • This will update the turbo.json file and try to install the latest version of turbo
    • In case of errors, you can manually update the turbo.json file following these steps
    • In case it wasn't possible to install turbo, try to do it manually:
      • yarn add -D turbo
    • Now you should be ready to use the latest version of turbo
• Eventually, update the workflow pointing to a specific SHA

[changeset-bot]

⚠️ No Changeset found

Latest commit: 175afe7

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[kin0992]

note: required to use proper version of yarn