Fixing host/insecure option handling in flyte-cli

Bump version (#74)

to 0.4.4

More auth configuration changes

Changes to Auth configurations (#68)

I realized while testing things a bit more locally that just having one endpoint was insufficient - flyte-cli and pyflyte currently leverage the gRPC Python Flyte Admin client.  However, discovery needs the HTTP endpoint.  Even though in production both are served on the same endpoint and traffic is handled through ingress, this is not always the case, and we want to support the use-case where gRPC Admin and HTTP Admin are hosted separately.

We were debating just adding a separate config for discovery alone, but ultimately it makes more sense to split out the existing URL config into two objects, especially if the above pattern is something we want to continue to support.  However, in the interest of not making people migrate, and not writing migration code in this PR, we're just introducing the HTTP one for now.

Also, we should lowercase the metadata header before sending it to Admin in the gRPC calls.

OAuth2 support for flyte-cli and SDK engine

OAuth2 support for flyte-cli and SDK engine (#23)

This change adds authentication support for flyte-cli and the pyflyte CLIs.

# New authorization code
Specifically this change introduces an **AuthorizationClient** which implements the [PKCE authorization flow](https://www.oauth.com/oauth2-servers/pkce/authorization-code-exchange/) for untrusted clients. This client handles requesting an initial access token, spinning up a callback server to receive the access token and using that to retrieve an authorization code. The client also handles refreshing expired authorization tokens.

This change also includes a lightweight **DiscoveryClient** for retrieving authorization endpoint metadata defined in the [OAuth 2.0 Authorization Server Metadata](https://tools.ietf.org/id/draft-ietf-oauth-discovery-08.html) draft document.

An authorization client singleton is lazily initialized for use by flyte-cli.

# Pyflyte changes (basic auth)
Requests an authorization token using a username and password.

# Flyte-cli changes (standard auth)
Requests an authorization token using the PKCE flow.

# Raw client changes
Wraps RPC calls to flyteadmin in a retry handler that initiates the appropriate authentication flow defined in the flytekit config in response to `HTTP 401 unauthorized` response codes.

Ability to specify IMAGE_NAME in build script

Ability to customize image name (#55)

This allows an override so that when we try to build images for git repos with multiple container images, we can customize the name.

Release: 0.3.0

v0.3.0

Release 0.3.0

[Beta]

https://pypi.org/project/flytekit/0.3.0b2/

v0.2.2

This version allows newer versions of protobuf

Rollup fixes on beta branch

Merge pull request #43 from lyft/0.3.0b1

Release v0.3.0b1

Single Hive query nodes

Instead of using the QueryCollection field.

[Testing] One query per Hive object

v0.1.8b1

reverting the change of the name