Fix workbench validation for CollectionObjectType

[sharadsw]

Describe the bug
From #5170: Workbench validation does not work when mappings involve CollectionObjectType

To Reproduce
Steps to reproduce the behavior:

1. Create a workbench dataset
2. Choose base table as CollectionObjectType or CollectionObject
3. Map a column to a relation with CollectionObjectType
4. Click validate
5. See error

Expected behavior
Workbench should be able to validate columns related to CollectionObjectType

Screenshots
From #5170:

chrome_frE2kFyiiK.mp4

[sharadsw]

AttributeError(\"module 'specifyweb.specify.models' has no attribute 'Collectionobjecttype'\")

Looks like an import error in the backend due to the model actually being named CollectionObjectType instead of Collectionobjecttype. It's happening with all geo tables.

The request payload being sent from the frontend when saving the upload plan mapper for the above dataset looks fine to me.

{
  "uploadplan": {
    "baseTableName": "collectionobject",
    "uploadable": {
      "uploadTable": {
        "wbcols": {
          "projectnumber": "Project Number",
          "fieldnumber": "Collection Object - GUID"
        },
        "static": {},
        "toOne": {
          "collectionobjecttype": {
            "uploadTable": {
              "wbcols": {
                "name": "Collection Object Type"
              },
              "static": {},
              "toOne": {},
              "toMany": {}
            }
          }
        },
        "toMany": {}
      }
    }
  }
}