[SYNPY-1349] Detect annotation type

[BryanFauble]

Problem:
Working with annotations was previously requiring a lot more verbose information. I was forcing a Type to be defined.

Solution:
Using the same logic that is in the current python client convert based off the class types into the appropriate type for the Synapse REST API. This allows us to simply define a list or singular annotation.

Testing:
See the test scripts.

[pep8speaks]

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

• In the file synapseclient/models/table.py:

Line 490:89: E501 line too long (91 > 88 characters)
Line 491:89: E501 line too long (92 > 88 characters)
Line 493:89: E501 line too long (89 > 88 characters)

• In the file test_scripts/oop_poc_file.py:

Line 85:89: E501 line too long (90 > 88 characters)

• In the file test_scripts/oop_poc_folder.py:

Line 80:89: E501 line too long (90 > 88 characters)

• In the file test_scripts/oop_poc_project.py:

Line 79:89: E501 line too long (90 > 88 characters)

• In the file test_scripts/oop_poc_table.py:

Line 128:89: E501 line too long (90 > 88 characters)

[thomasyu888]

I forget, but what does that convert function do when there are mixed types?

[BryanFauble]

It's returns an object which is than turned into a string:
nested_annos[key] = {"type": "STRING", "value": [str(e) for e in elements]}

[thomasyu888]

🔥 LGTM! Thanks for putting this together.