Bitbucket: remove special treatment of gravatar URLs

Revert 67200e5
Fixes #36

I honestly don't even remember why I added this. I think the goal was to correctly display the user name initials if they don't have a profile picture, but that use case seems to still work fine after removing this.

Author: pol-rivero

app/src/ui/lib/avatar.tsx

@@ -5,7 +5,6 @@ import { API, getDotComAPIEndpoint, getHTMLURL } from '../../lib/api'
 import { TooltippedContent } from './tooltipped-content'
 import { TooltipDirection } from './tooltip'
 import {
-  isBitbucket,
   isGHE,
   isGHES,
   supportsAvatarsAPI,
@@ -215,17 +214,6 @@ function getEmailAvatarUrl(ep: string) {
   }
 }
 
-function resolveBitbucketAvatarURL(avatarURL: string) {
-  const url = new URL(avatarURL)
-  if (url.hostname === 'secure.gravatar.com' && url.searchParams.has('d')) {
-    const d = url.searchParams.get('d')
-    if (d && d.startsWith('https://')) {
-      return d
-    }
-  }
-  return null
-}
-
 /**
  * Produces an ordered iterable of avatar urls to attempt to load for the
  * given user.
@@ -244,13 +232,6 @@ function getAvatarUrlCandidates(
   const { email, avatarURL } = user
   const ep = user.endpoint ?? getDotComAPIEndpoint()
 
-  if (isBitbucket(ep) && avatarURL) {
-    const resolvedAvatarURL = resolveBitbucketAvatarURL(avatarURL)
-    if (resolvedAvatarURL) {
-      candidates.push(resolvedAvatarURL)
-    }
-  }
-
   // By leveraging the avatar url from the API (if we've got it) we can
   // load the avatar from one of the load balanced domains (avatars). We can't
   // do the same for GHES/GHAE however since the URLs returned by the API are