Release/2.7.2

[siarheihuzarevich]

This pull request updates the workflow for publishing the m-render library on the release branch, introduces improvements to version handling, and updates the Node.js version used. It also includes a minor version bump in the m-render package.

Workflow updates:

• Renamed the workflow to "Publish m-render on Release" and changed the trigger from create to push on release/** branches. (.github/workflows/publish-on-release.yml, .github/workflows/publish-on-release.ymlL1-R4)
• Updated the Node.js version used in the workflow from 18 to 20. (.github/workflows/publish-on-release.yml, .github/workflows/publish-on-release.ymlL21-R21)
• Added logic to check if the version in libs/m-render/package.json matches the branch version before updating it. If the version is already correct, the update step is skipped. (.github/workflows/publish-on-release.yml, .github/workflows/publish-on-release.ymlL30-R52)
• Added steps to set up .npmrc for publishing and to create and push a git tag for the release version. (.github/workflows/publish-on-release.yml, .github/workflows/publish-on-release.ymlL50-R81)

Package updates:

• Bumped the version of libs/m-render/package.json from 2.7.0 to 2.7.2. (libs/m-render/package.json, libs/m-render/package.jsonL3-R3)