[US_TN] adding yaml for PREAScreeningResults (Recidiviz/recidiviz-dat…

…a#29504)

## Description of the change

We started receiving a new table from TN, PREAScreeningResults. This PR
adds the yaml for it so we can ingest it to BQ.

## Type of change

> All pull requests must have at least one of the following labels
applied (otherwise the PR will fail):

| Label | Description |
|-----------------------------
|-----------------------------------------------------------------------------------------------------------
|
| Type: Bug | non-breaking change that fixes an issue |
| Type: Feature | non-breaking change that adds functionality |
| Type: Breaking Change | fix or feature that would cause existing
functionality to not work as expected |
| Type: Non-breaking refactor | change addresses some tech debt item or
prepares for a later change, but does not change functionality |
| Type: Configuration Change | adjusts configuration to achieve some end
related to functionality, development, performance, or security |
| Type: Dependency Upgrade | upgrades a project dependency - these
changes are not included in release notes |

## Related issues

Closes #XXXX

## Checklists

### Development

**This box MUST be checked by the submitter prior to merging**:
- [x] **Double- and triple-checked that there is no Personally
Identifiable Information (PII) being mistakenly added in this pull
request**

These boxes should be checked by the submitter prior to merging:
- [x] Tests have been written to cover the code changed/added as part of
this pull request

### Code review

These boxes should be checked by reviewers prior to merging:

- [x] This pull request has a descriptive title and information useful
to a reviewer
- [x] Potential security implications or infrastructural changes have
been considered, if relevant

GitOrigin-RevId: 3e039fe74cb367977020e02172fdf8fc18a99746

recidiviz/ingest/direct/regions/us_tn/raw_data/us_tn_PREAScreeningResults.yaml

@@ -0,0 +1,56 @@
+# yaml-language-server: $schema=./../../../raw_data/yaml_schema/schema.json
+file_tag: PREAScreeningResults
+file_description: |-
+  This table contains one row for each PREA screening a given person has gone through a PREA (Prison Rape Elimination Act) Screening.
+data_classification: source
+primary_key_cols:
+  - OffenderID
+  - ScreeningDate
+columns:
+  - name: OffenderID
+    is_pii: True
+    description: |-
+      This is a unique identifier assigned to a particular person in the TOMIS system or a current, valid OBSCID ID number.
+  - name: ScreeningDate
+    description: |-
+      Date on which a screening takes place.
+  - name: ScreeningType
+    description: |-
+      This element describes a PREA screening type code
+  - name: ScreeningSiteID
+    description: |-
+      This identifies an organizational/location entity. This site will identify the institution where a PREA screening takes place.
+  - name: ScreeningBy
+    is_pii: True
+    description: |-
+      This is a unique identifier assigned to the staff ID who does a PREA screening.
+  - name: VictimFindingLevel
+    description: |-
+      Code indicating the PREA finding level for a victim.
+  - name: MonitorVictimFlag
+    description: |-
+      Indicates if an offender should have PREA monitoring for his VICTIM finding level.
+  - name: AggressorFindingLevel
+    description: |-
+      Code indicating the PREA finding level for an aggressor.
+  - name: MontorAggressorFlag
+    description: |-
+      Code indicating the PREA finding level for an aggressor.
+  - name: PostedByStaff
+    is_pii: True
+    description: |-
+      The staff id of the individual who initially posted information for an offender.
+  - name: PostedDate
+    description: |-
+      This is the date that data is actually posted to the system.
+  - name: LastUpdateStaffID
+    is_pii: True
+    description: |-
+      Staff ID of the last person to update a row on a table.
+  - name: LastUpdateUserID
+    is_pii: True
+    description: |-
+      This is the ID of the last person to access a table. This ID, combined with a timestamp, will provide an accurate audit trail to determine the last person to modify a table.
+  - name: LastUpdateDate
+    description: |-
+      This element will be associated with each record in each DB2 table in TOMIS.  It is the timestamp of the last time this record was updated.