[chore] Reverse changeset release flow

[art-alexeyenko]

• Reverts changeset flow

  • lerna does not update peerDependencies for canary or regular release. Was not a problem, until monorepo packages are added as peers. Needs another approach.
  • old lerna canary flow is tied to canary versions. Updating a single package creates a canary version for that package - but the rest of monorepo is not not using that canary, affecting testing. An alternative, snapshot canary approach is needed.

• applies canary versions for old flow

[github-actions]

📦 Package Size and Test Coverage Report

Package	Base Size	PR Size	Δ Change	Base Coverage	PR Coverage	Δ Change
analytics-core	60.99 KB	61.03 KB	🔺 +0.04 KB	100.00%	100.00%	0.00%
cli	59.14 KB	59.14 KB	✅ 0.00 KB	70.09%	70.09%	0.00%
content	424.56 KB	424.56 KB	✅ 0.00 KB	92.26%	92.26%	0.00%
core	119.33 KB	119.33 KB	✅ 0.00 KB	91.18%	91.18%	0.00%
create-content-sdk-app	335.50 KB	333.95 KB	🔻 -1.55 KB	96.35%	96.22%	-0.13%
events	66.35 KB	66.40 KB	🔺 +0.05 KB	98.13%	98.13%	0.00%
nextjs	478.49 KB	478.49 KB	✅ 0.00 KB	90.43%	90.43%	0.00%
personalize	63.95 KB	64.01 KB	🔺 +0.06 KB	99.74%	99.74%	0.00%
react	229.83 KB	229.83 KB	✅ 0.00 KB	93.68%	93.68%	0.00%
search	7.30 KB	7.30 KB	✅ 0.00 KB	98.57%	98.57%	0.00%
Total	—	—	🔻 -1.40 KB	—	—	—

[yavorsk]

Looks good.