OPSAPS-46858 Fix API version for 5.15.0

[bbhavsar]

pip installation for cm-api client is failing after CM API client was updated in 5.15.0 to v20. This appears to be due to incorrect upload of python egg package to external pypi.

For 5.15, there was no API version bump to v20, no new API endpoints added/modified/deleted. However there were changes to argument classes for missing fields mainly for BDR. OPSAPS-46448. Historically we appear to be bumping up CM API version every release which wasn't the case for 5.15.

For customers to get more recent version of cm-api python package from external pypi we'll need to bump up the version to like 19.1.0 to avoid confusion with CM API version. The version here is simply cm-api python package version.

There are more problems.

Since the internal starship/cm_api repo was updated to version v30 for cdep and internal consumption that has made it's way into external cm_api repository. This change fixes it.

This change will go directly to external cm_api repository.

Tests:

• sudo python ./setup.py install (From cm_api/python directory) Copying cm_api-19.1.0-py2.7.egg to /usr/local/lib/python2.7/dist-packages Adding cm-api 19.1.0 to easy-install.pth file Installing cmps script to /usr/local/bin

Installed /usr/local/lib/python2.7/dist-packages/cm_api-19.1.0-py2.7.egg Processing dependencies for cm-api==19.1.0 Finished processing dependencies for cm-api==19.1.0

[mostrows2]

LGTM

[kerneltime]

LGTM