verify the light-config-server response headers with jar file productId and version

[stevehu]

When asking for the config server to provide the configuration for a particular product (like http-sidecar and light-gateway), we need to verify if the productId and product version match the ones embedded in the jar file. If they are not matched, the server won't start. Another reason to have this validation is that the product version can be sent as current in the request and the config server knows which version is the default/current one. We need to make sure that the version matches the light-4j product version. For apiId, apiVersion and envTag, we need to verify against the startup.yml file configuration. This means the config server won't send us something we are not asking for.