SYNPY-316: Deprecate getProvenance and create get_activity

[BryanFauble]

Problem:
getProvenance is not a term defined in the REST docs - should be getActivity

Solution:

1. Create the new get_activity function and deprecated the old function
2. Updated all code I could find to use get_activity instead of getProvenance

Testing:

• I an all unit testing, relying on github pipeline for Integration testing

[thomasyu888]

I know this is in draft mode, but here's some initial comments

[thomasyu888]

We may have to add another parser so that people know that the cli

synapse get-provenance

is going to be deprecated. As it is written right now, the deprecation warning won't ever be triggered and we don't have synapse get-activity

[BryanFauble]

Got it - I will add in get-activity for the CLI.

What is the way to mark these are deprecated? I can add information into the help message like:
help="show provenance records. This is *deprecated* - Swap to using get-activity instead."

But is that sufficient?

[thomasyu888]

If you set the default function for get-provenance to be getProvenance, is it able to leverage the deprecated decorator?

Also - that might not be enough, so we could intentionally add a log.

[BryanFauble]

ok great - I am going to leave this calling getProvenance. In the console it prints out the warning:

DeprecationWarning: Call to deprecated function (or staticmethod) getProvenance. (deprecated and replaced with `get_activity`) -- Deprecated since version 3.1.0.

[pep8speaks]

Hello @BryanFauble! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found:

• In the file synapseclient/__main__.py:

Line 1436:89: E501 line too long (103 > 88 characters)
Line 1535:89: E501 line too long (101 > 88 characters)

[BryanFauble]

Closing PR for now - Will re-open at later date when thinking about jira: SYNPY-1303