Better template structure

[rndquu]

Based on this discussion and this PR we agree that right now the https://github.com/ubiquity/ts-template lacks structure and complex UIs (like pay.ubq.fi) are turned into a mess.

Since we don't want to use a js framework it makes sense at least to structure https://github.com/ubiquity/ts-template properly.

As as part of this issue the https://github.com/ubiquity/ts-template should be modified this way:

1. Add 2 separate html pages (example1, example2)
2. Add 2 separate js "controllers" for those html pages (example1, example2)
3. Add 2 reusable js components (example)
4. Add a router (example)
5. Add global on-load.ts and listeners.ts files for easier review and state management (not sure how it's gonna look like and if it's worth impleneting it)

In the end we should get a project structure similar to the one from https://github.com/vercel/next.js where it should be clear where exactly to put UI components, pages, handlers, etc...

[obeys]

/start

[ubiquity-os]

! This task does not reflect a business priority at the moment. You may start tasks with one of the following labels: Priority: 3 (High), Priority: 4 (Urgent), Priority: 5 (Emergency)

[ubiquity-os]

@obeys the deadline is at Wed, Dec 11, 11:01 PM UTC