feat(WebexMember): split component into space members and meeting participant

[thescripted]

Separate WebexMember intoWebexMember for spaces and WebexMeetingParticipant for meetings
Separate WebexMemberRoster intoWebexMemberRoster for spaces and WebexMeetingRoster for meetings

SPARK-308491
SPARK-308492

[taymoork2]

LGTM

[cipak]

Separate WebexMember intoWebexMember for spaces and WebexMeetingParticipant for meetings Separate WebexMemberRoster intoWebexMemberRoster for spaces and WebexMeetingRoster for meetings

SPARK-308491 SPARK-308492

This seems to introduce some code duplication, can this be avoided?

For example, leaving the generic WebexMember component as-is, and introducing two additional components:

• WebexSpaceMember
• WebexMeetingMember

These components would just use WebexMember with a hardcoded destination type, avoiding of duplication of js code and css:

function WebexSpaceMember(...) {
  return <WebexMember destinationType="ROOM" ... />;
}

Maybe the same could be done for the roster. I would suggest using the names WebexSpaceRoster and WebexMeetingRoster, so that the difference is clear: SpaceRoster vs MeetingRoster, instead of MemberRoster vs MeetingRoster which is a bit confusing.