Fix #186 - token and api endpoint not optional

[erichare]

Note that this applies specifically to the AstraDB (and async version) classes - for the Collection classes, one can provide either an astra_db instance already initialized OR pass a (token + endpoint). So those have been left as is.

[hemidactylus]

LGTM, just a question: is there any specific reason for replacing the **{...} unpacking of the credentials in the tests with explicit handling -- other than readability/aesthetics? (I mean, were there typing issues or something?)

[erichare]

LGTM, just a question: is there any specific reason for replacing the **{...} unpacking of the credentials in the tests with explicit handling -- other than readability/aesthetics? (I mean, were there typing issues or something?)

Yep, the reason was mypy. It didn’t like the fact that we are unpacking the credentials, because then it’s thinking that the required parameters are actually optional. I tried some kind of hacky workarounds, but in the end thought this was okay. If the universe of optional parameters expands though, we can restore the unpacking syntax for those, and just keep the required ones as explicitly provided.

hopefully that makes sense