Cleanups

[jacogr]

• Use new ~ URLs where applicable/missed
• Removed unused files
• Move files to correct locations
• Combine similar functionality into one file, multiple exports
• Remove unused styles

[derhuerst]

@jacogr

I put this here on purpose. The terms of service describe the legal implications of using the 3rd party service in 3rdparty/sms-verification. I can understand that having React in here feels weird, but since termsOfService is stateless & static, I think it's worth it. Having it in modals/SMSVerification/GatherData is very unintuitive imho.

[jacogr]

Very weird indeed, since the 3rdparty libraries are also stuff that we would like to start publishing under the @parity/ namespace. Unless we make an exception for the specific one and don't publish it at all.

[jacogr]

Ok, will revert that one, but breaks the purpose or the area. (Will have to treat it as "special and internal only")

[derhuerst]

I guess we have three choices.

1. not bundling the legal text with the library
2. using sth like dangerouslySetInnerHTML.
3. using plain text legal terms. they look less nice and the links are gone, but we still get rid of React.

[jacogr]

Suppose on #3, we could go with something like markdown - will actually kill 2 birds with one stone -

• be readable as text
• be transformable into pretty HTML

[derhuerst]

Markdown should get compiled on build. What about the template system currently in place? One you combine it with dangerouslySetInnerHTML.

[derhuerst]

Disagree with moving of termsOfService. Otherwise 👍 👍

[coveralls]

Coverage decreased (-0.03%) to 85.877% when pulling 8f81b10 on jg-housekeeping into f9a24f3 on master.