We update the existing patchRoleInfoWithSpecialRole utility used in the client migration to strip out the isDefault field from RoleInfo. It makes sense to include specialRole and exclude isDefault at the same time.

Depends on D11253

Re-run migration on web and native

1. Make sure all RoleInfos have the specialRole field included (can be null, but must be included)
2. Make sure all RoleInfos have the isDefault field removed.
3. Look at keyserver logIn response payload and ensure that specialRole IS included and isDefault ISN'T included