Feat: Support x-scapi-internal (@W-18760264@)

[joeluong-sfcc]

This PR adds support for the x-scapi-internal custom vendor extension. Whenever an operation is tagged as x-scapi-internal: true, we'll hide that operation from being generated in the SDK

Example:

    get:
      x-scapi-internal: true
      description: ...
      operationId: getProduct

There's unfortunately lots of duplicated code as we have to handle 2 cases

1. The operation has vendor extensions and x-scapi-internal is present
2. The operation has no vendor extensions

{{#vendorExtensions}}
{{^x-scapi-internal}}
// Render content for operations that have vendor extensions but NOT x-scapi-internal
{{/x-scapi-internal}}
{{/vendorExtensions}}
{{^vendorExtensions}}
// Render content for operations that have no vendor extensions at all
{{/vendorExtensions}}

[vcua-mobify]

Is the x-scapi-internal our alternative to having -internal and -public OAS specs? Or will we still have both of those after this change?

[unandyala]

Can you please explain what data gets passed into the included template? Is it the whole object or is is it based on the current context? May be add some comments in the template?

[joeluong-sfcc]

Is the x-scapi-internal our alternative to having -internal and -public OAS specs? Or will we still have both of those after this change?

No, we will still have 2 separate OAS specification files, the x-scapi-internal custom property will only be present in the internal OAS file

[vcua-mobify]

I've verified that when x-scapi-internal is added to an endpoint, that endpoint does not get added to the generated SDK.

Endpoints with other custom annotations that don't include x-scapi-internal will still appear.