Add support for new configs including advertised_port and use_secured_proxy

[YuWang24]

About this change - What it does

I am currently using a reverse proxy server (Nginx) in front of Karapace Rest Proxy. I am using the docker environment, and Nginx and Karapace are listening on different ports. When creating a consumer using Karapace:

curl -XPOST https://<domain>:<nginx-port>/consumers/consumer1 -u <username>:<password> \
--data '{"name": "my_consumer_instance", "format": "json", "auto.offset.reset": "earliest"}' \
--header "Content-Type: application/vnd.kafka.json.v2+json

The base_uri in response just gives me the karapace's port rather than the nginx port.
The response:
{"base_uri":"http://<ip>:<karapace-port>/consumers/consumer1/instances/my_consumer_instance","instance_id":"my_consumer_instance"}

Also, the protocol in the base_uri response is using http as default and cannot be changed because there are no configs to change that.

This PR adds support for new configs including advertised_port and use_secured_proxy to solve these problems.

New configs are added in karapace/config.py. And they are used in karapace/kafka_rest_apis/consumer_manager.py if these configs are set.

References: INS-18187

Why this way

[WeiXinFam-Insta]

LGTM

[vutdv-ic]

LGTM

[sujayinstaclustr]

LGTM