Update viessmann binding to use new viessmann domain

[rtuck99]

As part of the continuous optimization and modernization of our services, we are currently in the process of switching our applications and websites to the new domain viessmann-climatesolutions.com. This change will also affect the domains for resources such as the Developer Portal and the API Documentation.

For your integrations, this requires the following technical updates:

1. API Endpoints:
   The base URI for all API calls is changing. You need to update your code to use the new domain.
   Old: https://​api.​viessmann.​com/...
   New: https://​api.​viessmann-climatesolutions.​com/...

2. Identity and Access Management (IAM):
   The domain for our identity services will also be updated. This needs to be updated in your application to ensure authorization continues to function correctly.
   Old: https://​iam.​viessmann.​com
   New: https://​iam.​viessmann-climatesolutions.​com

3. API Response Body:
   The uri value within the JSON response from the Features API (/iot/v2/features/...) will reflect the new viessmann​-​climatesolutions.​com domain in the future.

The API endpoints under the new domain are already available, and we ask you to please use the new addresses with immediate effect. The old viessmann​.com domain will be deactivated during Q4/2025, by the end of the year at the latest.

We understand that these changes may require adjustments to your existing code. To assist you in this process, we recommend referring to the API documentation.

[AndreasBerz]

It should be possible to adjust/modify those "Default URLs" in the actual version of the API bridge at the configuration paramaters "Access Server URI" and "IoT Sercice endpoint". Has anyone tested that yet?

[agile-it]

I can confirm. This worked for me. I can provide a pull request if you want one.