Note that SciPy has a more elaborate method here, using
`IS_RELEASE_BRANCH`. Given that we're switching away from `setup.py` at
some point and the ship kind of has sailed for 1.21.x already,
I don't want to replicate that logic here.

This fixes setup.py to correctly detect the release status and base
version from the full version string provided by versioneer. Before
this fix, versions like '1.22.0.dev0+...' were correctly handled,
but versions like '1.21.0rc1+...' were not.

When creating the `bad_commands` dictionary it is useless to declare commands that are already set with a default message in the 329th line's for loop

This issue came in because of commit 9b3f65096e a month ago.
`bdist_egg` has always been missing from the command list, but
that wasn't a problem because missing commands were simply
ignored by the validation. After that commit we started raising
a RuntimeError instead.

MAINT: Add dist_info to "other" setup.py commands.

The follwing changes are made to 'setup.py'.

- Add 'dist_info' to the valid 'setup.py' commands. The 'dist_info'
  command was added to setuptools in 2017 and we were following the
  unrecognized command path in setup.py which raised a warning.
- Add 'version' to the recognized information commands, it came in with
  the move to versioneer.
- Include the arguments passed to 'setup.py' when the unrecognized
  command warning is raised. This will aid in maintaining the command
  checks in the future.

Before this change, it would give a random syntax error somewhere
in `versioneer`.