add patch 09 & 10

[VamshikShetty]

This PR contains following changes :

1. Introduction of patch 09 : Href schema model poses an issue where it is valid for most other models in anyOf scenario, hence by disabling allow additional properties we can fix this. This topic was discussed in a previous thread : Fix patches #61 (comment)

2. Introduction of patch 10, issue in InterconnectionPort schema :
   InterconnectionPort schema contains virtual_circuits attribute as a property:

properties:
  .
  .
  virtual_circuits:
    $ref: './VirtualCircuitList.yaml'
  .
  .
type: object

ref : https://github.com/equinix-labs/metal-java/blob/main/spec/oas3.fetched/openapi/public/components/schemas/InterconnectionPort.yaml

Whereas VirtualCircuitList represents a complex anyOf array for attribute named virtual_circuits :

properties:
  virtual_circuits:
    items:
      anyOf:
      - $ref: './VirtualCircuit.yaml'
      - $ref: './VrfVirtualCircuit.yaml'
    type: array
type: object

ref : https://github.com/equinix-labs/metal-java/blob/main/spec/oas3.fetched/openapi/public/components/schemas/VirtualCircuitList.yaml

This creates a incorrect response expectation which looks like this :

{
  "interconnectionport": {
    "virtual_circuits": {
      "virtual_circuits": [...]
    }
  }
}

Patch 10 create a file called InterconnectionPortCore.yaml file without virtual_circuits and uses allOf to merge this new file and VirtualCircuitList.yaml to create InterconnectionPort.yaml which gives the correct response flavour.

[ctreatma]

I think it would be more correct here to patch the VirtualCircuitList.yaml file to specify a list schema:

items:
  anyOf:
  - $ref: './VirtualCircuit.yaml'
  - $ref: './VrfVirtualCircuit.yaml'
type: array

[ctreatma]

Looking through the schema more, I see there's a lot of precedent for the current structure of VirtualCircuitList, and changing that would require a bigger patch, so I'm on board with what you have here.

One thing to note is that we're working on a patch to address #58, and that will likely include a name change for the VirtualCircuit model.

[ctreatma]

This is the right change IMO, but we should bear in mind that fixing it will likely uncover additional schema issues.