Overriding `md` with addExtension still reports `(liquid)` on the command line output

[zachleat]

Via https://starfallprojects.co.uk/blog/markdoc-eleventy/#enabling-markdoc

We don’t have a unique key or name for these addExtension when overrides are in place, so maybe just say (custom)?

[Snapstromegon]

Maybe even allow providing a name for your "engine" and it could fall back to "(custom)" or always be "(custom/{{configured_name}})". We could call that field simply "name" or "compilerName" or similar.

[Snapstromegon]

One additional question would be, wether or not to always mark a custom engine as (custom) even on newly defined extensions (like .clowd). I would say so.

[zachleat]

Fixed by #2481, shipping with 2.0.0-canary.19!

[zachleat]

cc @StarfallProjects whose blog post inspired this one!