feat(aktuelt): minimal viable info pages

[niccofyren]

Closes: #8

Similar to (and extending) #9 this PR exposes pages on http://localhost:8000/api/v2/info with semi-realistic fields.

More details in previous PR, but a few additional questions

• How to best expose a tree of pages via API? It seems like Wagtail expect to mostly list a single level at a time, unless using relational fields (outside of basic page model) or manually listing fields. First option introduces a separate structure level that we don't want, and second option seems to require us to have duplicate serialization logic. One clean (but inefficient) option would be to list types and ids and leave it to frontend code to get actual objects.