GAIA-26824 Remove the get_access_token from sdk and --print_token from cli

[prabesh-paudel]

Goal/Problem:
With auth0, we no longer allow people to specify username and password to get their access token.
So get_access_token function, that allows people to use their username and password to fetch their access token needs to be removed.

We can see no calls to /api-token from non webapp origin with username and passwd for last 4 days. Kibana.

Solution.
Remove the get_access_token function from sdk and --print_token argument from cli.

Testing
Tested importing get_access_token: from groclient.lib import get_access_token throws an error as expected.
Tested gro_client:

python -m groclient --item=sesame --region=ethiopia works. (env variable is set)
python -m --item=sesame --region=ethiopia  --user_email prabesh throws error as expected
python -m --item=sesame --region=ethiopia  --print_token throws error as expected.
python -m --item=sesame --region=ethiopia  --token ... works.
python -m groclient --item=sesame --region=ethiopia without token gives error as expected. AssertionError: Need --token, or the access token to be set in environment variable: $GROAPI_TOKEN

[daire-gro]

looks good to me! are there any automated tests that we need to update in this repository?

[daire-gro]

@prabesh-paudel there are two other places that seem to mention 'user_email' param

README.md
46: gro_client --metric="Production Quantity mass" --item="Corn" --region="United States" --user_email="[email protected]"

docs/quick-start-projects/gro_client-tool.rst
8: gro_client --metric="Production Quantity mass" --item="Corn" --region="United States" --user_email="[email protected]"

[prabesh-paudel]

@prabesh-paudel there are two other places that seem to mention 'user_email' param

README.md 46: gro_client --metric="Production Quantity mass" --item="Corn" --region="United States" --user_email="[email protected]"

docs/quick-start-projects/gro_client-tool.rst 8: gro_client --metric="Production Quantity mass" --item="Corn" --region="United States" --user_email="[email protected]"

Great catch. I just updated it. Thank you !!

looks good to me! are there any automated tests that we need to update in this repository?

I can't find any more references to the get_access_token or user_email and the unit test seems to pass, so I guess no..