[Typescript Conversion: Level 18]: Convert ui/components/ui/page-container/page-container-footer/page-container-footer.component.js to typescript

Nobody has claimed this yet.

## **Description**

Convert `ui/components/ui/page-container/page-container-footer/page-container-footer.component.js` from JavaScript to TypeScript as part of the TS migration initiative.

## **Scenario (for user stories only)**

_(Not applicable)_

## **Design (for user stories only)**

_(Not applicable)_

## **Technical Details (for technical tasks only)**

- Convert this file to TypeScript.
- Migration Level: **18**
- Dependencies:
- ui/components/ui/button/index.js
- Dependents:
- ui/components/app/modals/qr-scanner/qr-scanner.component.js
- ui/components/app/qr-hardware-popover/base-reader.js
- ui/components/ui/page-container/page-container-footer/index.js

## **[Threat Modeling Framework](https://github.com/adamshostack/4QuestionFrame) (for technical tasks only)**

- What are we working on? Convert file to TypeScript.
- What can go wrong? Type errors, integration mismatches, missing types.
- What are we going to do about it? Write types carefully and test thoroughly.
- Did we do a good job? _(To be evaluated)_

## **Acceptance Criteria**

- File is fully converted to TypeScript.
- Tests pass.
- File adheres to linting rules.
- Functionality remains unchanged.

## **Stakeholder Review (for MetaMask employees only)**

- [X] Engineering
- [ ] Design
- [ ] Product
- [ ] QA
- [ ] Security
- [ ] Legal
- [ ] Marketing
- [ ] Management
- [ ] Other

## **References**

- Parent issue: #31460

Start with ui/components/ui/page-container/page-container-footer/page-container-footer.component.js and review its dependency on ui/components/ui/button/index.js. Convert the named component to TypeScript while preserving functionality, then check the listed dependents and run the project's tests and lint checks to confirm the acceptance criteria.

Written by the indexing model from the issue text.