vh_matches paths ignored on create/update/import of VirtualService

[tthrone-atomic]

Describe the bug

When using Enhanced Virtual Service setup, we always receive the the following error
HTTP code: 400; error from Avi: map[error:{"vh_matches":"{"path":"Field check for path failed : There must be at least 1 path"}"}]

Additionally, when importing an enhanced virtual service with valid vh_matches configuration into local state, the vh_mathes field is always null.

Reproduction steps

1. Configure valid parent VVS resource
2. Configure valid child VVS resource
3. Apply
4. Receive error: HTTP code: 400; error from Avi: map[error:{"vh_matches":"{"path":"Field check for path failed : There must be at least 1 path"}"}]

Expected behavior

Virtual Service creation should succeed with the specified path configurations provided.

Additional context

`
resource "avi_virtualservice" "child" {
name = "example-child"
type = "VS_TYPE_VH_CHILD"
vh_type = "VS_TYPE_VH_ENHANCED"
vh_parent_vs_ref = avi_virtualservice.parent-vs.id

vh_matches {
  host = "test.example.com"
  rules {
    name = "test"
    matches {
      path {
        match_str = ["/test"]
        match_criteria = "BEGINS_WITH"
        match_case = "INSENSITIVE"
      }
    }
  }
}

}
`

[chandanapatnala]

Hi ,
Can you please mention the version of the controller too

[tthrone-atomic]

Controller is 21.1.4