Correct v4 checking to include future versions of the API

The v4? check was only pinning on :v4 versions of the API. This patch now
allows for future versions to match also, and so I've renamed it to v4-and-newer?

Also, remove-status was pinned to :v4, and is now future compatible.

Signed-off-by: Ken Barber <ken@bob.sh>