chore: remove near-sdk-sim from repo

[austinabell]

Since there is no way for us to upgrade near-sdk-sim to be compatible with new protocol version, it is necessary we not just soft deprecate and if people need these sim tests, they can stay on 4.0.0-pre.9 until they can switch

Closes #662
closes #802
closes #759

[willemneal]

Good riddance! No more rocksdb artifacts blowing up my hard drive.

[ChaoticTempest]

Feels like people can benefit from us publishing one final patch release to near-sdk-sim to say it's deprecated and workspaces should be used in favor. WDYT?

[austinabell]

Feels like people can benefit from us publishing one final patch release to near-sdk-sim to say it's deprecated and workspaces should be used in favor. WDYT?

That's why I released 4.0.0-pre.9, it's unlikely people would update into any temporary version we release in the ~week between now and stable release.

Obviously not ideal, but it wasn't foreseen that we would have to hard deprecate sim tests for 4.0 given we can't update the VM logic. We can add a commit on top of the released commit as a patch version, but I'm not sure that's better since it will be the last functional version of the SDK for near-sdk-sim and dealing with deprecation warnings might not be ideal either.

[itegulov]

Can we just delete all the code but leave a top-level #[deprecated] annotation that leads the user to workspaces-rs and migration doc and release it as a 4.0 version for the very last time?

[austinabell]

Can we just delete all the code but leave a top-level #[deprecated] annotation that leads the user to workspaces-rs and migration doc and release it as a 4.0 version for the very last time?

The reason this is not done is because the code will be broken using 4.0 of the SDK and will be cryptic why it doesn't work. We can always release a 4.0 with this deprecation based on this old commit, but since it's not functional anymore we should remove it from the repo.

Let's find some time to chat about the best path for this as it's a bit nuanced.

Options being:

• Add deprecation to sim tests on 4.0 release (even though broken on sim tests)
• Add compiler error on the 4.0 release with links to workspaces (and migration doc if stable link)
• Do not release near-sdk-sim and just communicate this deprecation to community

Any of these can be done if this PR comes in, though

[itegulov]

Yeah fair enough