Upgrade to omniauth-alicloud 3.0.0

What does this MR do and why?

• Includes MR: gitlab-jh/jh-team/omniauth-alicloud!6 (merged)
  • change use userinfo.sub instead of userinfo.uid as alicloud omniauth uid.
• Upgrade to omniauth-alicloud 3.0.0
  • This change is not compatible

The aliuid is not required in alicloud oauth page, if user not choose the aliuid option, we could not get the uid from the userinfo api. Then Identify.extern_uid column will be blank after user connects to alicloud (I'm wondering why the Identify.extern_uid column doesn't need to have a presence validation check). So we need to change use userinfo.sub instead of userinfo.uid as alicloud omniauth uid. The openid is always required in alicloud oauth page and the userinfo.sub is aways exsits in the api.

alicloud oauth page	userinfo api

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before	After

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.