Update release instructions

The step of bumping the `package.json` version was only for Quicksight,
as it isn't used by PureScript package managers. Quicksight no longer
uses this library, so we can get rid of the step.

Author: Dave Zuch

package.json

@@ -1,6 +1,5 @@
 {
   "name": "purescript-ocelot",
-  "version": "0.35.0",
   "private": true,
   "scripts": {
     "build-all": "make build",

readme.md

@@ -46,9 +46,6 @@ Our built CSS is version controlled, so that consuming applications can use it w
 
 To create a new release:
 
-1. Adjust the version in `package.json`.
-    Some of our dependents rely on this version being correct.
-1. Submit the changes to `main` via a PR.
 1. Create a tag for the version.
     ```sh
     $ git tag $NEW_VERSION