fix(canonical-title-map): add use case for enumNames

[jmfrancois]

Description

Add support case for enumNames.
Spec: json-schema-org/json-schema-spec#57

We have some schemas with the following shape:

{
  "jsonSchema": {
    "type": "object",
    "title": "Datalist",
    "properties": {
      "test": {
        "type": "string",
        "enum": [ "a", "p", "b", "c", "l", "g" ],
        "enumNames": [ "Apple", "Pine[apple]", "Banana", "Cher[ry", "Lemo}n", "Grapefruit" ]
      }
    },
    "required": [
      "test"
    ]
  },
  "uiSchema": [
    {
      "key": "test",
      "title": "Datalist with named options",
      "widget": "datalist"
    }
  ],
  "properties": {
    "test": "Pine[apple]"
  }
}

This raise exception with the current implementation because we have an array of value for the titleMap;

Checklist

• I have read and understand the CONTRIBUTIONS.md file
• I have searched for and linked related issues
• I have created test cases to ensure quick resolution of the PR is easier
• I am NOT targeting master branch
• I did NOT include the dist folder in my PR

@json-schema-form/angular-schema-form-lead

[scottux]

This definition of canonical doesn't seem to be used. I think it is safe to remove it.

[scottux]

remove trailing comma here.