chore: logic for replacing version

[mertmit]

Change Summary

• Depending on workspace: ^ we need to manually push that change to master after release, we can instead use package name to replace the version
  (see rn after the release master have versions instead of workspace: ^)
• Add --ignore-workspace for pnpm install of nocodb-sdk as we need to publish before bumping other packages

Change type

• chore: (updating grunt tasks etc; no production code change)

[github-actions]

Uffizzi Ephemeral Environment deployment-39080

☁️ https://app.uffizzi.com/github.com/nocodb/nocodb/pull/6759

📄 View Application Logs etc.

What is Uffizzi? Learn more!

[wingkwong]

If using a release version, then all sdk changes done in locally won't reflect in local dev, fe & be will take the version of the release one instead of local one.

[mertmit]

Yes we should definitely target local after releases (even we can improve our release action to revert it back when finished) but imo it shouldn't break the release actions if something goes wrong with that.
So if this doesn't cause an extra issue might be good to have.