near-mpc-sdk should have a separate version field than the workspace version

[DSharifi]

Background

The near sdk currently inherits the cargo workspace version. We should decouple it, so that we can set separate versions for the SDK.

The motivation is that we want to be able to have separate relsease schedules and semver versioning for this crate, so it should not use the workspace version which is strictly tied to the contract and node bundle.

User Story

No response

Acceptance Criteria

near-mpc-sdk has its own versioning

Resources & Additional Notes

No response