Global configuration for functions

[lance]

Allow the user to set global configuration options, for example the image registry, with func config --global.

[nainaz]

Context

Enterprises and developers using the same configuration parameters that may be different from the default ones for creating functions currently has to change the values repeatedly. Cluster admin would like to set up the common and standard parameters for the developers

Story

As Dina the developer, I should be able set some global configuration parameters across my machine/cluster so that I can have the same configuration override applied to all my functions and not fiddle with the default ones provided every time.

As cluster admin, I should be able set some global configuration parameters across my machine/cluster so that I can have the developers user the consistent approved configuration values override applied to all functions created in the org 

Acceptance Criteria

GIVEN that I provide the global override of configuration parameter 
WHEN I write and create my functions
THEN globally set configurations should be used rather than the default ones while building and deploying my function.

[lance]

/kind epic

[knative-prow]

@lance: The label(s) kind/epic cannot be applied, because the repository doesn't have them.

In response to this:

/kind epic

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[github-actions]

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

[github-actions]

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.

[matejvasek]

/remove-lifecycle stale

[github-actions]

This issue is stale because it has been open for 90 days with no
activity. It will automatically close after 30 more days of
inactivity. Reopen the issue with /reopen. Mark the issue as
fresh by adding the comment /remove-lifecycle stale.