YOTI HUB service creation improvments

CONTEXT

Any customer that wants to use Yoti services in production has to create a service.
‍
A service is effectively an ‘instance’ of one of Yoti products, with a few attributes:

- Product (IDV / AVS etc)
- Configuration (product-specific settings)
- Collaborators (Users able to see Portal sessions related to this service)

Depending on the product that a customer is looking to use, the service creation process can have a significant amount of settings that a customer may need to adjust.

problem

Users didn't understand what an “application” (terminology has changed to "service" as part of this project).

For users creating an IDV service (majority), there were a lot of settings they are expected to configure, which they often don't understand.

We had one service creation flow, even though API vs Portal customers have different needs and expectations.

For No-code users, the service creation process added unnecessary complexity.