[#45] Destruction list detail view

[SilviaAmAm]

Fixes #45

[Xaohs]

The landing page doesn't do this either right now, but I think we should think about combining some of the things here like the STATUS_MAPPING and the formatUser() since the landing page also uses them (and possibly others later on). For example a function formatUser() that takes in some options to customize the output would be nice, and a central place to get the status mappings from.
I think we can ignore it for now though

[SilviaAmAm]

I moved the status mappings to a constants.ts files and the format user function to a utils file. Then it can be more easily reused by the landing page. Then we can expand the options once we have a better idea of what we need!

[Xaohs]

Just to make sure, what happens if we hit this return?

[SilviaAmAm]

The UI crashes, because the loader didnt return anything 😄 I changed it to make it return an empty dict, and then the DestructionListDetailPage renders a (temporary) 404 page.

[Xaohs]

Why is this type assertion (and similars in the render) needed? Don't we already type assert it higher up the tree at line 30?
const { zaken: allZaken, zaaktypeChoices } = useLoaderData() as DestructionListDetailContext;

[SilviaAmAm]

In DestructionListDetailContext they are defined as PaginatedZaken and allZaken.results is then Zaak[]. I added it to make it stop complaining about it :S

[Xaohs]

Hmm yeah, the DataGrid component expects AttributeData[] array I guess, a bit sad that these things aren't compatible, should be ok then haha