web/satellite: update and optimize error page

[boshevski]

What:
Use 3x smaller size background image and update styles. Update button.

Why:
We were updating the error page for linksharing, and using the same optimized background now updating the satellite error page. Also we are not using rounded buttons anymore.

Please describe the performance impact:

Code Review Checklist (to be filled out by reviewer)

• NEW: Are there any Satellite database migrations? Are they forwards and backwards compatible?
• Does the PR describe what changes are being made?
• Does the PR describe why the changes are being made?
• Does the code follow our style guide?
• Does the code follow our testing guide?
• Is the PR appropriately sized? (If it could be broken into smaller PRs it should be)
• Does the new code have enough tests? (every PR should have tests or justification otherwise. Bug-fix PRs especially)
• Does the new code have enough documentation that answers "how do I use it?" and "what does it do?"? (both source documentation and higher level, diagrams?)
• Does any documentation need updating?
• Do the database access patterns make sense?

[jewharton]

Although this path is functional at runtime, it produces an unresolved path error when building. It should be expressed relative to the current file: ../../static/images/errors/world.svg.

[boshevski]

Thank you Jeremy!