Fix mustache template: Only add the deprecation message to the Obsolete-tag if it exists

[Kwok-he-Chu]

Description
This PR addresses the [Obsolete]-tag in the model and service mustache templates. These should only be shown if the message is available in the specs.

Tested scenarios

Example with CardDetails.cupsecureplusSmscode

Before:

[Obsolete("Deprecated since Adyen Checkout API v -")]

After:

[Obsolete("")]

I kept the template easy-to-read, I didn't want to make an exception for the empty case, e.g. just[Obsolete] without the double quotes and brackets ("")

---

Example with just the deprecation version:

[Obsolete("Deprecated since Adyen Checkout API v37.")]
        Model.Checkout.PaymentSetupResponse PaymentSession(PaymentSetupRequest paymentSetupRequest = default, RequestOptions requestOptions = default);

---

Example with the deprecation message and version:

[Obsolete("Deprecated since Adyen Checkout API v49. Use `storedPaymentMethodId` instead.")]
        public string RecurringDetailReference { get; set; }

[gcatanese]

Changes are fine.

Keep into consideration that for the endpoints there is the x-deprecatedInVersion extension without vendorExtensions.x-deprecatedMessage, in this case the formatting could look wrong.
Suggestions:

• check also if x-deprecatedMessage is available
• format the message differently, instead of using - use a .

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[gcatanese]

Changes are good

If you like check the changes in Java app where I have updated the templates to check separately for the 2 extensions (without assuming message is provided when version is found)

Adyen/adyen-java-api-library@be75d2d