Seemingly pbxproj broke.

This reverts commit dd3c5b1c.

Rating+UI had assorted test code and lacked documentation.

* PEMA-246:
  PEMA-246 - remove whitespace
  PEMA-246 - remove link
  PEMA-246 - add link to credits

Disabled state hasn't been fully defined, but this will do until it is.

Removed old icons that are no longer used.

Removed Color+UI as it wasnt used anymore.
Rating+UI now takes over all the duties it had.

Now that all the UI-elements are generated from Rating instead of Color, usage of color+UI has been reduced.

Added Darkmode .pdf

New icons need handling (msg vs no msg)
Will check how to handle disabled states, and if they are even needed on Rating+pEp

Added missing icons

Added guard let construct
Properly intended messages
Fixed incoherent messages (sometimes no email provider name, sometimes it had it on ouath)

After reading the code review the following changes have been added:
-Made isCloud less exposing to inner data.
-Added descriptor for LoginProtocol
-Added guard let to most functions in LoginUtil and those using callbacks from it.

OIDAuthState should not exist (moved to messagemodel)

After review, most classes had small issues with their formating or location, as such the following has been fixed:
Added proper tab and formating for them
Renamed certain classes to keep within expected logic (CamelCase, OIDAuthState+JWT)
Moved OIDauthState to messagemodel along with most OAuth adjacent classes where it should be.
Changed OIDAuth signature to remove references to things the class shouldn't know (such as the name of fields inside the JWToken) 
Refractored OAuth2AccessToken and protocol to fit with being able to give email and name from the JWToken.

Further cleaned up the classes, added less strange ways to set up things and removed oddities like an initialise function which didn't make much sense, as the protocol doesn't really care how you handle your responses.

Cleaned up code, removed old dead code and added placeholder tests.
Additionally added comments to the stranger functions (OIDauth extension).

Added temporary test placeholders.

Added abstraction class for login, it should handle all cases and all internal login logic (saving data, etc...) only returning an error state or a success state.

Adjusted both LoginViewModel and AccountTypeSelectorViewModel to work with it, along with that AccountTypeSelectorViewModel now properly logs the user.

Extended OIDAuthState to parse JWTokens.

TODO: 
Make VM/VC more cohesive between both with marks, etc...
Troubleshot bugs.
Pass tests and update them with the new login logic.
Move and re-name new classes to their proper places in the internal structure and logic of the project.
Cleanup the new classes.
PEMA-309 Fixed bug

UI was set to be permanently loading, it isn't anymore.

The process to log in via OAuth2 is now seamless, when the OAuth logging button is pressed and post segue to the login screen, the OAuth2 process will be automatically launched and all the important user data will be set directly from the OAuth request.

TODO: Properly review if moving all the login in logic to a helper would make it cleaner (as to avoid repeating this logic in both the login VM and account type select VM.
TODO: Move the JWT logic to it's own class or library to mirror android and avoid dependency bloat.

Office 365 demands to add OpenID scope, google does not

Acquiring the display name is possible via adding the proper scope (profile), which means that the UI should seamlessly log into oath accounts.

Note that the JWT might be updated or changed, as such to cope with that the token fields should be gotten on call instead of being static.

Made OAuth2 automatically set up the email, this is done via adding the scope OpenID and Email so the idToken outputs a parseable JWT which contains the field email.

TODO: Clean up code, remove email field (leave only user field) in case profile does not output username.

Office 365 demands to add OpenID scope, google does not

Acquiring the display name is possible via adding the proper scope (profile), which means that the UI should seamlessly log into oath accounts.

Note that the JWT might be updated or changed, as such to cope with that the token fields should be gotten on call instead of being static.