Consolidate all the "status" enums

[Jericho]

@MacgyverH and I were having a discussion on a PR he was working on and it led us to realize that there are several enums in the ZoomNet library that are used for "status" properties on various models despite the fact they all have the same possible values. It would make sense to have only one enum and to reuse it when possible.

I performed a cursory search and found three such enums (but there could be more):

• UserStatus
• ReportHostType
• PollStatusForEventSession

Also, let's not fprget the newly added CallQueueStatus.

[MacgyverH]

How do we want to address the extra values such as the pending option for User status? I don't believe pending status is used in these other cases, I don't think I have stumbled across this anywhere else either.

I presume these same enums would/could be used to post data to the API right? In which case we will want to ensure that only valid values are available I would assume?

[Jericho]

Maybe UserStatus is a special case and it needs it's own enum. Maybe none of these enums are ever used to POST to the API and they are simply used when parsing data returned from the API in which case it doesn't matter if there are extra values in the enum. I haven't put that much thought into it yet.

But the point remains that we need to make an effort to consolidate as many enums as possible and avoid creating new enums with the same values when possible.

[MacgyverH]

I'm in agreement with this thought. 🙂

[MacgyverH]

@Jericho Another thing I noticed that might be troublesome & need to be considered, "Activate" vs "Active" and "Inactive" vs "deactivate" values.

[Jericho]

Mapping multiple strings to a single enum value is a scenario we faced before and I have a solution for it. Here's an example how we handle it:

https://github.com/Jericho/ZoomNet/blob/develop/Source/ZoomNet/Models/ParticipantDevice.cs#L29-L33