Merge openmetadata.yaml and openmetadata-server.yaml

[harshach]

Feature
Currently we keep non-secure configs in openmetadata.yaml and secure configs openmetadata-server.yaml.
Our ./bin/openmetadata-server-start.sh uses conf/openmetadata.yaml as the default config
It not only confuses our users but also hard to make the docker to go from non-secure to secure setup.

Describe the task
Have all the secure configs in openmetadata.yaml with authenticationConfiguration and authorizerConfiguration along with environment variables to secure those.
By default these will have non-secure configs. This will allow any interested users to continue to test OpenMetadata without securing through google or okta

[harshach]

@Sachin-chaurasiya @darth-coder00 currently the UI tries to redirect the UI to auth provider if it sees authenticationConfiguration.
With this patch we want to support both secure/non-secure using environment variables.
Default configs you'll get

{
provider: "no-auth",
publicKey: "https://www.googleapis.com/oauth2/v3/certs",
authority: "https://accounts.google.com/",
clientId: "",
callbackUrl: ""
}

if you see no-auth do not redirect users to sign-in. This behavior should be same as when the user doesn't have any auth