Incorrect error message creating Cache Group with no typeId

[ocket8888]

I'm submitting a ...

• bug report

Traffic Control components affected ...

• Traffic Ops

Current behavior:

Creating a Cache Group without specifying its Type (via the typeId property) gives the error message:

"missing type"

Expected behavior:

Should name the actual missing property: typeId.

Minimal reproduction of the problem with instructions:

Create a Cache Group without specifying it's type by ID, but providing the type property mentioned in the error message e.g.

{"name": "test", "type": "anything"}

Anything else:

HTTP Stack

POST /api/2.0/cachegroups HTTP/1.1
User-Agent: python-requests/2.24.0
Accept-Encoding: gzip, deflate
Accept: */*
Connection: keep-alive
Cookie: mojolicious=...
Content-Length: 28

{"name": "test", "type": 23}

HTTP/1.1 400 Bad Request
Access-Control-Allow-Credentials: true
Access-Control-Allow-Headers: Origin, X-Requested-With, Content-Type, Accept, Set-Cookie, Cookie
Access-Control-Allow-Methods: POST,GET,OPTIONS,PUT,DELETE
Access-Control-Allow-Origin: *
Content-Encoding: gzip
Content-Type: application/json
Set-Cookie: mojolicious=...; Path=/; Expires=Tue, 17 Nov 2020 02:28:43 GMT; Max-Age=3600; HttpOnly
Vary: Accept-Encoding
X-Server-Name: traffic_ops_golang/
Date: Tue, 17 Nov 2020 01:28:43 GMT
Content-Length: 77

{
        "alerts": [
                {
                        "text": "missing type",
                        "level": "error"
                }
        ]
}

[rimashah25]

I can take this one.