(ci) Update npm-publish workflow for 1st party actions, permissions and node

[turbobobbytraykov]

Updated workflow to use newer action versions and added permissions for id-token and contents - just like in the master branch
+
updated actions/checkout to v7
+
updated node 20 -> 24

Description

Make sure we are aligned with the current practices that are already applied to the master branch.

Related Issue

N/A

Type of Change

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update
• Refactoring / code cleanup
• [x ] Build / CI configuration change

Affected Packages

• [x ] igniteui-cli (packages/cli)
• [x ] @igniteui/cli-core (packages/core)
• [x ] @igniteui/angular-templates (packages/igx-templates)
• [x ] @igniteui/angular-schematics (packages/ng-schematics)
• [x ] @igniteui/mcp-server (packages/igniteui-mcp)

Checklist

• I have tested my changes locally (npm run test)
• I have built the project successfully (npm run build)
• I have run the linter (npm run lint)
• I have added/updated tests as needed
• My changes do not introduce new warnings or errors

Additional Context

N/A

[coveralls]

coverage: 70.252%. remained the same — btraykov/update-publish-workflow into vNext

[damyanpetev]

@turbobobbytraykov it'd appear the publish workflow is already updated to actions@6 and node 24 looking at the state in master:

igniteui-cli/.github/workflows/npm-publish.yml

Lines 15 to 18 in bd0bcea

	- uses: actions/checkout@v6
	- uses: actions/setup-node@v6
	with:
	node-version: 24

https://github.com/IgniteUI/igniteui-cli/blob/master/.github/workflows/npm-publish.yml

Thus the conflicts :)

[damyanpetev]

I believe this is already validated on CI level - i.e. the version is committed content, validated on PR. This might be redundant.

[damyanpetev]

Suggested change

	echo ${NPM_TAG}

Or echo "${NPM_TAG}" will do too - I think it's still valid.

Just would really prefer a single pattern of interpolating env. variables and we're already accessing ${VERSION} with brackets and run deploy ${NPM_TAG} below, etc :)