juju-k8s-crashdump must also collect ConfigMaps

This could be as easy as adding another resource type to collect [here](https://github.com/canonical/juju-k8s-crashdump/blob/0d02b49cd8c7e2dbb580dca20504561745b79e1c/juju_k8s_crashdump/main.py#L136), and will help debug failures stemming from ConfigMaps.

Additionally, it is probably also relevant to also collect the `-config.yaml` output of `juju config -o yaml` for all applications in the model.

Start in juju_k8s_crashdump/main.py around line 136, where the collected resource types are defined. Trace the existing crashdump collection flow and determine how to include ConfigMaps and each application's `juju config -o yaml` output; done means both appear in the generated crashdump.

Written by the indexing model from the issue text.