Create Table: UserIntakeTargetSkillXref

### Overview

We need to create the UserIntakeTargetSkillXref table to support many-to-many relationship between User and Skill.

#### Details

A table and a model are the same thing

### Action Items

- [ ] Identify if table has a description (see spreadsheet under Resources)
- [ ] If not, reach out to PD leads
- [ ] Create a single model in Django (defining schema)
- [ ] Write a test for the relationships this model will have with other models (e.g., creating a user and assigning them a set of permissions on a project).
- [ ] Write an API end point
- [ ] Write API unit tests
- [ ] Document the endpoint in Swagger

### Resources/Instructions

- See [People Depot Resources wiki page](https://github.com/hackforla/peopledepot/wiki/Resources-and-Links) for links
- ERD
- Table and Field Definitions
- API Endpoint
- See [this Wiki page](https://github.com/hackforla/peopledepot/wiki/Create-Table-issues-data-gathering-workflow) for instructions on the data-gathering workflow for Create Table issues

### Items to document (referenced above)

- Confirm the table description and relationships against the spreadsheet and ERD.

#### Description

- Cross-reference table associating users with their intake target skills.

### Data Fields

- [ ] Copied from spreadsheet and confirmed according to ERD

| Name | Type | FK Table | FK Table Issue(s) |
| ---- | ---- | -------- | ----------------- |
| user | int | User | #15 |
| skill | int | Skill | #38 |

### FK status

- #15 - closed
- #38 - closed

Start with the People Depot Resources wiki, especially the ERD, spreadsheet, API endpoint details, and Create Table workflow. Confirm the table description, relationships, and fields for User and Skill, then follow the checklist for the Django model, relationship tests, API endpoint, API unit tests, and Swagger documentation. Done means all listed items are confirmed and tested.

Written by the indexing model from the issue text.