Simplify release process for example measurements

Tech Debt

https://github.com/ni/measurement-plugin-python/wiki/Release-Process has manual pre/post-release steps dealing with example versioning. I think we can simplify this by leaving the path = "../../..." dev-dependencies uncommented in the Git repo and updating the publish workflow to comment them out before building the examples .zip file. This is basically what we have been doing with packages/generator for the 2.1.0 release.

The current process was established before we started building a separate examples .zip file. At that time, users were expected to obtain the examples by cloning the Git repo or downloading the per-release .zip file containing the entire Git repo checked out at the release tag. Now that we are building a separate examples .zip file, we can modify the examples before zipping them up.

Note that you can use poetry install --only main to ignore dev-dependencies.

Cc: @dixonjoel @rajatkumar87

AB#2903024

Start with the release-process wiki page and the publish workflow, then compare its example packaging with the packages/generator process used for 2.1.0. Use poetry install --only main to verify the examples work with development dependencies left in the repository; done means the workflow comments those dependencies before creating the examples .zip file.