FalcoSidekick chart redis connectivity inconsistent and disallows DB spec for webui

[clearclaw]

The falcosidekick chart allows redis connectivity to be defined in two places, once in the config for storing events which takes an address, a port and a database number as distinct values, and again for the webui which takes a url and port number. Further, the webui redis connection spec insists on bolting a port number onto the end of any provided URL in the deployment, and passing the URL and port separated to redis-cli in the initcontainer.

The core problem is that the web-ui spec does not allow the database number to be specified and eg the following values break:

  falcosidekick:
    config:
      redis:
        address: 10.1.2.3
        database: 14
    webui:
      enabled: true
      externalRedis:
        enabled: true
        url: redis://10.1.2.3:6379/15

Suggest that both allow the entire URL (ie redis[s]://[[username][:password]@][host][:port][/db-number]) be supported for both connections (including rediss for TLS), and that both also allow using an external secret containing the full URL instead for eg user/pass offloading. Note: redis-cli accepts a -u argument which takes a standard Redis URL as above, instead of the -h and -p used now.