customize export kinds in markdown

[bennypowers]

What I Did

1. Wrap Markdown name column value in backticks
2. Separate static fields and methods from instance in markdown
3. add exportKinds option to to-markdown and README, which lets the use replace js and custom-element-definition with strings of images by URL
4. bump versions

[netlify]

❌ Deploy Preview for custom-elements-manifest-analyzer failed.

🔨 Explore the source changes: 5a96a12

🔍 Inspect the deploy log: https://app.netlify.com/sites/custom-elements-manifest-analyzer/deploys/60eaf7defe1a3600077456ea

[thepassle]

I think we need to communicate better. I took this to mean we're not adding md functionality to the analyzer directly, but shipping the plugin instead

[bennypowers]

not adding md functionality to the analyzer directly, but shipping the plugin instead
I'd be keen to move the cli code to the plugin as well i'm just not sure how to proceed. maybe we'd have the cli entrypoint scan for plugins and augment its own args definitions?

[thepassle]

maybe we'd have the cli entrypoint scan for plugins and augment its own args definitions?

This seems like a bad idea to me. If a user wants to add plugins they should use the config file

[thepassle]

Not sure what to do with this PR now, it has changes that we dont really have consensus on (or had discussed to handle otherwise), has multiple changes that are not really related to eachother... Maybe we revert the --readme flag commit, find consensus on what to do with it, and move forward with the changes to to-md and cem-plugin-readme separately?

[bennypowers]

Removed the --readme flag from this PR, will open another draft to explore the idea