fix(sharing): Handle memory leak in self removal

- A memory leak / bad component rerender in
sharingProvider seems to lose react props when
removing self from a sharing.
As a result, this will cascade in the react tree and end
in an unhandled crash that will kill the app completely (blank page).
- To fully handle this issue there is also something to handle
on cozy drive side
- Still, the root cause of the error has not been found yet.
But the error is severe enough to need this local fix

packages/cozy-sharing/src/components/Avatar/MemberAvatar.jsx

@@ -4,10 +4,21 @@ import { useClient } from 'cozy-client'
 import Avatar from 'cozy-ui/transpiled/react/Avatar'
 
 import { getDisplayName, getInitials } from '../../models'
+import logger from '../../logger'
 
 const MemberAvatar = ({ recipient, ...rest }) => {
   const client = useClient()
 
+  // There are cases when due to apparent memory leaks, the recipient does not exist
+  // This will trigger an unhanded error in the Avatar component and crash the app
+  // At the moment, we are not sure where is the root cause of this cascading undefined props
+  // Nevertheless, we can prevent the crash by returning null if the recipient is undefined
+  if (!recipient) {
+    // eslint-disable-next-line
+    logger.warn('RecipientAvatar: recipient is missing, see props:', { recipient, ...rest })
+    return null
+  }
+
   /**
    * avatarPath is always the same for a recipient, but image
    * can be different since the stack generate it on the fly.