Add -draft to development hardware spec version

[jonnew]

• Fixes Give WIP spec version a "draft" suffix #83

[jonnew]

@bparks13 For some reason these changes are not being reflected in the build artifact and I wonder if it has to do with the multi-version stuff.

[bparks13]

@jonnew You are correct, this is related to the sphinx-multiversion extension. I documented this behavior in the README, with the relevant sentences copied here for convenience:

ONI/README.rst

Lines 94 to 102 in 9a50996

	It is also important to note that if you
	are working in a feature branch, it is not automatically pulled into the build
	due to the branch whitelist found in the conf.py file. To test changes
	that have been committed locally, add the current branch to the
	``smv_branch_whitelist`` regular expression. For example, if the current working
	branch is ``issue-XX``, then the new regular expression can be modified to be
	"r'^(main|issue-XX)$'". Be sure to revert the changes to the conf.py file before
	merging to main, otherwise the feature branch will be built in the online
	version.

Basically, the build process for sphinx-multiversion is not governed by the local files themselves, but by the branches that are configured to be built. To test local changes, the local branch must be added to the build process.

To confirm, I added issue-83 to the whitelist to be built, which gave me the following build artifact:

[jonnew]

Thanks, as per our discussion lets do the following: #85.