chore: delete std-client package

[holic]

depends on #1339

need to leave the package.json behind until we have an answer from changesets/changesets#1215

[changeset-bot]

🦋 Changeset detected

Latest commit: 50ffc62

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 27 packages

Name	Type
@latticexyz/std-client	Major
@latticexyz/block-logs-stream	Major
@latticexyz/cli	Major
@latticexyz/common	Major
@latticexyz/config	Major
create-mud	Major
@latticexyz/dev-tools	Major
@latticexyz/ecs-browser	Major
@latticexyz/gas-report	Major
@latticexyz/network	Major
@latticexyz/noise	Major
@latticexyz/phaserx	Major
@latticexyz/protocol-parser	Major
@latticexyz/react	Major
@latticexyz/recs	Major
@latticexyz/schema-type	Major
@latticexyz/services	Major
@latticexyz/solecs	Major
solhint-config-mud	Major
solhint-plugin-mud	Major
@latticexyz/std-contracts	Major
@latticexyz/store-cache	Major
@latticexyz/store-indexer	Major
@latticexyz/store-sync	Major
@latticexyz/store	Major
@latticexyz/utils	Major
@latticexyz/world	Major

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[alvrs]

since there are still a couple projects using the action queue, i wonder if we should keep this in some other package? can mark it as deprecated but i feel bad about fully removing it without an alternative option for easily handling optimistic updates. A satisfying replacement could be as simple as a util to define an optimistic update that is removed once the tx is confirmed / all state updates triggered by the tx are reduced.

[holic]

Folks can still pin to the old version via npm if they need to stick on the old version for now. And that's an easy to add util, but would be curious to find folks actually using it, how they're using it, and make sure we're providing the right abstractions over it.

Alternatively, we could just move this to the RECS package.

[alvrs]

We can find projects still using it via https://github.com/search?q=createActionSystem+std-client&type=code. It's true that folks can still pin to the old version, but I feel like we should encourage staying up to date with the latest version and make upgrading as easy as possible. The path of least resistance would be moving it to the recs package (and still marking it as deprecated and adding a note for how if no "requirements" are needed there is no need to use the action system, and maybe adding a simple util like

mud/docs/pages/tutorials/emojimon/players-and-movement.mdx

Lines 303 to 315 in ce7125a

	const positionId = uuid();
	Position.addOverride(positionId, {
	entity: playerEntity,
	value: { x, y },
	});
	try {
	const tx = await worldSend("move", [x, y]);
	await awaitStreamValue(txReduced$, (txHash) => txHash === tx.hash);
	} finally {
	Position.removeOverride(positionId);
	}
	};

as alternative for the use case of managing optimistic updates)

[holic]

hmm there's still some reliance on ethers and txReduced$ in here 🙈

so I guess createActionSystem isn't even compatible with the v2 stack as it is

[holic]

I was able to port most of it over: #1351

But realizing that tests are failing and I'm not sure when they last passed (because we haven't had this package running tests in CI for at least a year).