FSS data types in docstring too verbose about scores

[tennlee]

I think this is because of the compound types in scores.typing.
Another downside of type hinting
Ideally, I would prefer the type hints didn't appear in the function signature area at all, but did appear in the arguments table. I find with the type hinting in the function signatures it's just overwhelming to read. I'm not sure if there's anything configurable in the doc generation toolchain that would let us configure this.

[nikeethr]

https://www.sphinx-doc.org/en/master/usage/extensions/autodoc.html#confval-autodoc_typehints

setting this to "description" maybe.

[nikeethr]

Ok turns out this is due to setting the default threshold arg to np.greater; strange that it didn't cause issues with other "callables" in e.g. event operators. I've changed it to optional and default to None and resolving it to np.greater within the function(s).

Still quite verbose, but at least its consistent with the rest of the docs.

[tennlee]

Checkout https://scores.readthedocs.io/en/228-documentation-testing-branch/api.html to see what happens if I change that variable to 'description'. Looks great to me, what do you think?