Give shared components explicit prop types

[RaymondAbiola]

Summary

Some shared components accept loosely typed props, which makes them easy to misuse and hides mistakes until render time. Tightening the types moves those errors to the typecheck.

Acceptance criteria

• Shared components declare explicit prop types.
• Optional props declare their defaults.
• The typecheck passes with no behaviour change.

Getting started

Fork this repository, clone your fork, and add this repo as upstream:

git clone https://github.com/<your-username>/tricklepay-frontend.git
cd tricklepay-frontend
git remote add upstream https://github.com/TricklePay/tricklepay-frontend.git

Create a branch for this issue:

git checkout -b refactor/issue-163

Suggested commit message:

refactor: tighten shared component prop types

Run npm run lint, npm run typecheck, npm test, and npm run build before opening a pull request and linking this issue.

[Indo86]

Hi! I'd like to work on this issue.

I've forked the repository, created refactor/issue-163, and reviewed the shared components. My plan is to replace inline/anonymous prop object types on shared exported components with explicit named prop types, and declare defaults directly for optional props where applicable, without changing runtime behavior.

I also ran the baseline checks on the latest upstream/main. I noticed that npm run typecheck, some tests, npm run build, and lint currently have pre-existing failures unrelated to this issue.

I'll keep the changes for #163 scoped only to component prop typing. Please let me know if you'd prefer a different scope or expect the existing baseline failures to be addressed separately.