feat: Implement profile picture #343

[hubsMIT1]

Fixes Issue #343

**My PR closes #343 **

👨‍💻 Changes proposed(What did you do ?)

• Created a UserAvatar file for profile picture
• Added schema for profile image
• Used Google Vision API to check unsafe content in pictures

✔️ Check List (Check all the applicable boxes)

• My code follows the code style of this project.
• This PR does not contain plagiarized content.
• The title and description of the PR is clear and explains the approach.

Note to reviewers

📷 Screenshots

https://drive.google.com/file/d/1A10Gfon7JnLGqyImLPX62llo6RC-LrrK/view?usp=sharing

[vercel]

Someone is attempting to deploy a commit to a Personal Account owned by @Dun-sin on Vercel.

@Dun-sin first needs to authorize it.

[github-actions]

PR Compliance Checks Passed!

[Dun-sin]

please spread the props like other components, then use proptypes. you can see what i mean by looking at other components and this should be in the component folder but the pages' folder because it's a component not a page.

[hubsMIT1]

Done!

[mathiasayivor]

Can the docs also be updated on how to configure vision?

[Dun-sin]

Can the docs also be updated on how to configure vision?

Let the PR be merged first, I will but there's no point when it's not yet merged, like chill

[hubsMIT1]

Can the docs also be updated on how to configure vision?

Let the PR be merged first, I will but there's no point when it's not yet merged, like chill

should I update?

[Dun-sin]

Can the docs also be updated on how to configure vision?

Let the PR be merged first, I will but there's no point when it's not yet merged, like chill

should I update?

Yes it's much better you do it, so it all gets merged together. Add it to the Readme steps.

[Dun-sin]

You did great, thanks for implementing my changes