Avatar uploading should use more sensible handling

[MasterInQuestion]

    E.g. https://avatars.githubusercontent.com/u/81106051
    (~ 349.24 KiB; PNG: RGB, 460x460)

    Compare: https://github.com/MasterInQuestion/attach/raw/main/MasterInQuestion/.avatars/poise.webp
    (~ 309.4 KiB; WebP Lossless: 725x725) [1]

    Besides the missing support for an influential format.
    The uploading may regardless choose the recompressed the image for no good: when the original is smaller.
    Somewhat comparable: https://github.com/go-gitea/gitea/issues/8972#issuecomment-1542513735

[ [1]
    Anything larger than 460x460 gets down-scaled; probably suboptimally, to 460x460.
    Uploading a 460x460 one did return an image of identical effective information. (though might of bloated size)
    [ ^ Tested PNG. Unsure what happens for JPEG. (possibly double-compression?) ]

    The documentation probably needs update:
    https://docs.github.com/en/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile#changing-your-profile-picture
    "Your profile picture should be a PNG, JPG, or GIF file, and it must be less than 1 MB in size and smaller than 3000 by 3000 pixels. For the best quality rendering, we recommend keeping the image at about 500 by 500 pixels."
    .
    Why the excessive confusion, when the precise expectation is 460x460?

    Note:
    The default identicons are 420x420.
    As mentioned:
    [ Quote redoubledit @ CE 2018-02-22 21:46:13 UTC:
https://old.reddit.com/r/github/comments/7zhxx1/github_profile_picture_help/?sort=old#duo9oen
    The default GitHub profile img is 420x420 px. Maybe try that? ] ]


=== See also ===

    Please allow SVG profile pictures
    https://github.com/orgs/community/discussions/7878

    Native WebP image support
    https://github.com/orgs/community/discussions/5470

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐