[admin v3] add WorldUsersProvider to fix 💣

[denisdimitrov]

WorldUsersProvider wrapper needs to be added to admin v3 to fix the crashing of the page. This might need some research on how to be done correctly since there are multiple v3 pages that can be accessed. Maybe the initial one would be enough if they are in the same sub router.

Here is the fix for admin v1:
#1757 (comment)

[0xdevalias]

I think this may have been resolved by some of the work @goran-peoski-work did the other day with the <Provided withWorldUsers withRelatedVenues> component.

We should find/link that PR here, and if it resolves this issue, then we can close it off, etc.

[goran-peoski-work]

There are few PRs that touch on providers for Admin (v1,v2,v3):

• fix Error: <WorldUsersProvider/> not found in a more holistic way #1769 - adds the Provided component for adding providers to specific routes
• Use EmptyProvider instead of React.Fragment in Provided #1797 - removes minor console log annoyance about props usage on <></>
• remove fetching all venues across the codebase #1620 - adds administered venues provider

[whoaitsaimz]

Hey @ermiaSparkle can we confirm if this is done? Issue was created on the public repo.

[ermiaSparkle]

Qa and close it tomorrow

[whoaitsaimz]

It's a question for @mike-lvov