Convert Text files to PDF

* As a ministry coordinator
* I want text files to be converted to PDF when I upload them into the Records log
* so that the files can be added to the linear Harms PDF for review and be reviewed in the Records Review app

**Assumptions & Scope**
The Records Review app cannot view TEXT. Will convert to PDF.

What is in and not in scope?
Upload and dedupe by metadata has is covered in task #3465

**Acceptance Criteria**

**Scenario 1: Convert TEXT files to PDF **
* GIVEN a Ministry coordinator is on the records log
* WHEN the ministry coordinator uploads Text files to the Records log
* THEN the Text files will be converted to a PDF
* AND the Text file will show with as a PDF on the log with a green check mark
* AND a copy of the record in the original file format will be kept

...

**Dependencies? What is the impact of this dependency? (If so, link dependency in the ticket, make it visible in a team?s backlog)**

**Validation Rules? (If yes, list here)**

**Design**
@xxx - please link the Design here

**Definition of Ready**

1. [ ] Is there a well articulated User Story?
2. [ ] Is there Acceptance Criteria that covers all scenarios (happy/sad paths)?
3. [ ] If there is a user interface, is there a design?
4. [ ] Does the user story need user research/validation?
5. [ ] Does this User Story needs stakeholder approval?
6. [ ] Design / Solution accepted by Product Owner
7. [ ] Is this user story small enough to be completed in a Sprint? Should it be split?
8. [ ] Are the dependencies known/ understood? (technical, business, regulatory/policy)
9. [ ] Has the story been estimated?

**Definition of Done**

1. [ ] Passes developer unit tests
2. [ ] Passes peer code review
3. [ ] If there's a user interface, passes UX assurance
4. [ ] Passes QA of Acceptance Criteria with verification in Dev and Test
5. [ ] Confirm Test cases built and succeeding
6. [ ] No regression test failures
7. [ ] Test coverage acceptable by Product Owner
8. [ ] Ticket ready to be merged to master or story branch
9. [ ] Developer to list Config changes/ Update documents and designs
10. [ ] Can be demoed in Sprint Review
11. [ ] Tagged as part of a Release
12. [ ] Feature flagged if required
13. [ ] Change Management activities done?

The issue names no implementation files or tests. Start by locating the Records log upload flow and reviewing the scope in task #3465; done means uploaded text files appear as PDFs with a green check mark while a copy in the original format is retained, with unit and acceptance tests passing.

Written by the indexing model from the issue text.