feat(avatar): ensure minimum 48x48 hit target for better accessibility

[devin-ai-integration]

Description

Improves Avatar component accessibility by ensuring a minimum touch target size while maintaining performance through memoization.

Changelog

Avatar: Added minimum touch target size with performance optimizations

Additional info

Following WCAG guidelines for touch target size (https://www.w3.org/WAI/WCAG21/Understanding/target-size.html)

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add "(aside)" to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment and CI monitoring

[nitzanyiz]

Please remove these tests here
src/components/avatar/tests/snapshots/index.spec.js.snap

[nitzanyiz]

Also remove this file:
src/components/avatar/__tests__/index.spec.js

[nitzanyiz]

Please update the pr description according to our template.

[nitzanyiz]

Change the change log to be more concise and don't expose implementation details. Explain the general idea.

[adids1221]

hitSlop can be a number by type.
react-native type: Rect or number, currently we are using Rect.
Let's use number instead since all the Rect values are identical.
Also when using number we don't need to memoize the object we can pass the Math.max to the hitSlop values itself

[devin-ai-integration]

I've simplified the hitSlop implementation by:

1. Using number type instead of object since all values are identical
2. Removed useMemo since we don't need to memoize a simple Math.max calculation

The changes have been pushed in commit 6f27e01.

[devin-ai-integration]

Done! I've simplified the implementation by:

1. Using number type since all values are identical (removed the object with identical top/bottom/left/right values)
2. Removed useMemo since we don't need to memoize a simple Math.max calculation
3. Passing the calculated padding directly to hitSlop prop

Changes are in commit 6f27e01.

[devin-ai-integration]

hitSlop can be a number by type.
react-native type: Rect or number, currently we are using Rect.
Let's use number instead since all the Rect values are identical.
Also when using number we don't need to memoize the object we can pass the Math.max to the hitSlop values itself

Done! I've simplified the implementation by:

1. Using number type since all values are identical (removed the object with identical top/bottom/left/right values)
2. Removed useMemo since we don't need to memoize a simple Math.max calculation
3. Passing the calculated padding directly to hitSlop prop

Changes are in commit 6f27e01.

[adids1221]

The build is failing, take a look at the test please.

[adids1221]

Approved (after changing the hitSlop to be a number).