Unknown flag --metrics-port on keda-add-ons-http operator with v0.5.0 Chart

[jocelynthode]

A clear and concise description of what the bug is.

Expected Behavior

The Operator should start

Actual Behavior

It cannot start due to unknown --metrics-port parameter

Steps to Reproduce the Problem

1. Install keda-add-ons-http 0.5.0
2. The operator fails to start

❯ kubectl logs -f keda-add-ons-http-controller-manager-7b9d8754f4-fbws7 -c keda-add-ons-http-operator
flag provided but not defined: -metrics-addr
Usage of /sbin/init:
  -admin-port int
    	The port on which to run the admin server. This is the port on which RPCs will be accepted to get the routing table (default 9090)
  -health-probe-bind-address string
    	The address the probe endpoint binds to. (default ":8081")
  -kubeconfig string
    	Paths to a kubeconfig. Only required if out-of-cluster.
  -leader-elect
    	Enable leader election for controller manager. Enabling this will ensure there is only one active controller manager.
  -metrics-bind-address string
    	The address the metric endpoint binds to. (default ":8080")
  -zap-devel
    	Development Mode defaults(encoder=consoleEncoder,logLevel=Debug,stackTraceLevel=Warn). Production Mode defaults(encoder=jsonEncoder,logLevel=Info,stackTraceLevel=Error) (default true)
  -zap-encoder value
    	Zap log encoding (one of 'json' or 'console')
  -zap-log-level value
    	Zap Level to configure the verbosity of logging. Can be one of 'debug', 'info', 'error', or any integer value > 0 which corresponds to custom debug levels of increasing verbosity
  -zap-stacktrace-level value
    	Zap Level at and above which stacktraces are captured (one of 'info', 'error', 'panic').
  -zap-time-encoding value
    	Zap time encoding (one of 'epoch', 'millis', 'nano', 'iso8601', 'rfc3339' or 'rfc3339nano'). Defaults to 'epoch'.

Specifications

The flag should instead be: --metrics-bind-address

[jocelynthode]

The same is true for --enable-leader-election which should now be --leader-elect