Enable Auth Metadata Local Caching in Flyte-SDK

[edwardsun-union]

- Description

Based on the decision make in eng slack channel. We have decided to enable auth metadata local cache capability in order to reduce the unnecessary GetPublicClientConfig API calls currently existing when executing common tasks such as flyte run workflow. As part of the decision, the cache will be stored within the hidden .flyte directory under home based on the OS.

- Testing

before change:

1. In local env, create a new config. Example:
   flyte create config --endpoint dns:///dogfood.cloud-staging.union.ai --project edward-test --domain staging --image-builder remote
2. executing flyte task using the create config. Example test command below:
   flyte -vvv -c ./.flyte/config.yaml run ./basics/types/int_collection.py main --numbers '[1,2,3,4,5,10,20,30]'
   For client configuration refer to dogfood staging config v2
3. GetPublicClientConfig call occurs for every task run

after change:

1. repeat the same test steps.
2. cache file contains auth metadata is generated and stored with all required auth metadata
3. Repeat the same flyte task run
4. observed that GetPublicClientConfig API call is not made from Grafana (To differentiate traffic from local env, temporarily bump up connectrpc minor version to such as connectrpc/0.10.1)

[pmahindrakar-oss]

Is this needed

[edwardsun-union]

this is for enabling breakpoint to help debugging, added as dev dependency only, should be no harm

[edwardsun-union]

@pmahindrakar-oss the audience is already refreshed from PublicClientConfig Call here