ZEVA2 - user story - ICBC file upload

**Description:**
- [ ] As a government user, I want to upload files containing vins and other vehicle data so that I can use the uploaded data to validate applications for credits associated with the supply of EVs.

**Wireframe:** Please see zeva1 for inspiration.

**Purpose and benefit to user:**
This supports a legislative requirement.

**Acceptance Criteria:**

- [ ] Given I am a government user, when I upload an ICBC file, then associated data in zeva2 gets created/updated (and deleted?)

**Development Checklist:**
- [ ] Create the models that support the ICBC data
- [ ] Create the API that interacts with nrm object storage/minio (can use zeva1's dev object storage credentials for local development; if there are CORS issues that can't be resolved, you can define a minio service in docker-compose and use that).
- [ ] Investigate whether we can do a chunked upload using bullmq (analogous to how we do a chunked upload of the ICBC file in CTHUB) so that users can upload without using a preprocessor.
- [ ] Create the action(s) that support(s) the uploading of the file.
- [ ] Create the client/supporting components that support the uploading of the file.

**Notes:**
One may wish to chat with someone from the business area regarding what exactly happens when an ICBC file gets uploaded; for example, perhaps one should ask them if a subsequent file should "override" a previous file. More specifically, if file1 is an earlier file and file2 is a later file, and file1 marks vin X as an EV, but file2 says vin X is not an EV, should we delete vin X from our list of EV vins?