chore: add accessibility props to components and screens

[fc-santos]

Summary of Changes

This PR adds accessibility props to components/screens that were missing it.

Screenshots, videos, or gifs

N/A

Breaking change guide

N/A

Related Issues

N/A

Pull Request Checklist

Tick all boxes below to demonstrate that you have completed the respective task. If the item does not apply to your this PR check it anyway to make it apparent that there's nothing to do.

• All commits contain a DCO Signed-off-by line (we use the DCO GitHub app to enforce this)
• If applicable, screenshots, gifs, or video are included for UI changes
• If applicable, breaking changes are described above along with how to address them
• Updated documentation as needed for changed code and new or modified features
• Added sufficient tests so that overall code coverage is not reduced

If you have any questions to any of the points above, just submit and ask! This checklist is here to help you, not to deter you from contributing!

Pro Tip 🤓

• Read our contribution guide at least once; it will save you a few review cycles!
• Your PR will likely not be reviewed until all the above boxes are checked and all automated checks have passed

[al-rosenthal]

if these aren't rending text we should just remove them and add padding if we need the space

[bryce-mcmath]

The vast majority of these changes are great, but I agree with Alfred that we should remove the empty <Text> tags

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[fc-santos]

@bryce-mcmath Are you able to tell why my last two PR's that were merged into main failed on the Alpha Release step ? I checked the logs and it's weird.

[bryce-mcmath]

@fc-santos It is weird! I'm looking into it but so far I don't know what is causing it. All of the latest npm alpha versions are at 400 and the latest github tag is 400, but it's attempting to publish 402 instead of 401. That could have something to do with it but I'm pretty sure it's been able to skip a version in the past and still publish without issue.