feat: proxy component

[hetangmodi-crest]

Issue number: ADDON-72372

Summary

Similar to logging component, we now have a proxy component, also introduced a new argument --need-proxy which includes default proxy configuration during init method

Changes

• Just like logging component we now have a new type proxyTab which gives default proxy configuration, so that user doesn't have to mention default configuration themselves they just have to mention their custom configurations.

• Introduced a new argument in init method that is --need-proxy, which includes default proxy configuration in globalConfig.json during creation of new add-on.

• Changed the approach of fetching proxy_details inoauth template file. For that created a function in solnlib which fetches proxy_details and validates proxy_host and proxy_port.

User experience

Changes according to UX point of view :

• If user have to use our default configuration of proxy they just need to define type=proxyTab in their globalConfig.
• They can add their custom validations for any field, but they would have to use some specific keys for that
  for ex. If a user wants to customize the label of port they would just have to write
  { "type": "proxyTab", "port": { "label": "Proxy port", } }
• Now users can validate their port and hostnames of proxy through get_proxy_dict function of solnlib.
• While initializing an add-on user will have extra parameter --need-proxy which includes default proxy configuration in globalConfig.json.

Checklist

If your change doesn't seem to apply, please leave them unchecked.

• I have performed a self-review of this change
• Changes have been tested
• Changes are documented
• PR title follows conventional commit semantics

[artemrys]

@hetangmodi-crest please fix pre-commit.