Fix the issue with logging when there are multiple error causes

[yogeshnikam671]

What:
When we have multiple error causes, Specmatic used to log only the single cause out of it as an error message.
This PR fixes that issue and logs all the error messages encountered.

e.g. Suppose we have a schema with examples as follows -

openapi: 3.0.1
info:
  title: OpenAPI definition
  version: v0
servers:
  - url: http://localhost:8080
    description: Generated server url
paths:
  /customers:
    post:
      tags:
        - customer-controller
      operationId: saveCustomer
      requestBody:
        required: true
        content:
          application/json:
            schema:
              oneOf:
                - $ref: '#/components/schemas/CustomerAddress'
                - $ref: '#/components/schemas/Customer'
            examples:
              CUSTOMER_ADDRESS:
                summary: Example of a customer address object
                value:
                  id: 1
                  customerId: 1005
                  houseNo: '1234'
                  street: 'B.St'
                  city: 'Melbourne'
                  state: 'Victoria'
                  postCode: '3000'
                  requestType: 'address'
              CUSTOMER:
                summary: Example of a customer object
                value:
                  id: 104
                  customerId: 1004
                  initial: J
                  #firstName: John
                  secondName: Doe
                  customerType: GOLD
      responses:
        "200":
          description: OK
          content:
            'application/json':
              schema:
                oneOf:
                  - $ref: '#/components/schemas/CustomerAddress'
                  - $ref: '#/components/schemas/Customer'
              examples:
                CUSTOMER_ADDRESS:
                  summary: Example of a customer address object
                  value:
                    id: 1
                    customerId: 1005
                    houseNo: '1234'
                    street: 'B.St'
                    city: 'Melbourne'
                    state: 'Victoria'
                    postCode: '3000'
                    requestType: 'address'
                CUSTOMER:
                  summary: Example of a customer object
                  value:
                    id: 104
                    customerId: 1004
                    initial: J
                    firstName: John
                    secondName: Doe
                    customerType: GOLD
components:
  schemas:
    Customer:
      required:
        - customerType
        - firstName
        - initial
        - secondName
      type: object
      properties:
        id:
          type: integer
          format: int32
        customerId:
          type: integer
          format: int32
        initial:
          type: string
        firstName:
          type: string
        secondName:
          type: string
        customerType:
          type: string
          enum:
            - BRONZE
            - SILVER
            - GOLD
            - PLATINUM
        verified:
          type: boolean
    CustomerAddress:
      type: object
      properties:
        id:
          type: integer
          format: int32
        customerId:
          type: integer
          format: int32
        houseNo:
          type: string
        street:
          type: string
        city:
          type: string
        state:
          type: string
        postCode:
          type: string
        requestType:
          type: string

In the above specification, I have commented out the firstName key from the CUSTOMER example.
If we try to run Specmatic tests using such schema, it should definitely break since the CUSTOMER example is not satisfying any of the schemas defined.

Ideally, Specmatic should compare this example with both the oneOf schemas and log the respective error messages.

Specmatic does compare the example with both the schemas but while logging it logs only a single error message as follows -

This PR fixes that and logs all the respective error messages -

Why:
Specmatic was not logging all the error message due to a very minor bug where we were not returning the error message when there are multiple error causes.

How:
The PR fixes the bug by simply returning that error message.

Checklist:

• [] Documentation added to the README.md OR link to PR on https://github.com/specmatic/specmatic-documentation
• Tests
• Sonar Quality Gate

[joelrosario]

Looks good to me.