Update maintenance

Include new step about docs,
and remove last step replaced by CI step

Author: adespawn

MAINTENANCE.md

@@ -93,18 +93,12 @@ Remember to run `npm i` in the `examples/` and `benchmark/` directories once you
 the main directory, `examples/`, and `benchmark/`. You can do this by running `npm i` in all 3 directories
 (see [example commit](https://github.com/scylladb/nodejs-rs-driver/pull/363/changes/41250609737052975129c7514439869324478008) on how to do that).
 3. Create a new tag.
-4. Ensure the extended CI passes.
-5. Create release notes on GitHub. The version tag must match version from `package.json` with `v` prefix (for example: `v0.2.0`).
+4. Add the new tag to the documentation configuration (see #470)
+5. Ensure the extended CI passes.
+6. Create release notes on GitHub. The version tag must match version from `package.json` with `v` prefix (for example: `v0.2.0`).
 Once you publish release notes, CI action will trigger automatically. This action will build and publish the npm package.
-6. Once the CI action finishes, check if it succeeded. If it failed, you will have to fix the underlying issue, and re-run the CI action.
-7. Verify that the new release is visible at [npmjs site](https://www.npmjs.com/package/@scylladb/driver).
-8. Test the package, by installing it directly from npm. Go to `examples` directory, in `package.json` update the line:
-`"@scylladb/driver": "file:./../"`
-to:
-`"@scylladb/driver": "<just-released-version>"`,
-then run the following command:
-`npm i && node ./runner.js`
-<!-- The last step can potentially be set up as a CI action step. -->
+7. Once the CI action finishes, check if it succeeded. If it failed, you will have to fix the underlying issue, and re-run the CI action.
+8. Verify that the new release is visible at [npmjs site](https://www.npmjs.com/package/@scylladb/driver).
 
 ### Updating packages