Preparing ex_doc to switch to EarmarkParser

[RobertDober]

Well maybe this is a little bit early, Earmark will remain at your disposal if you prefer

If you want to wait until Earmark uses EarmarkParser for some versions or not switch at all I will not be offended (well not much)

However ultimately I'd like to use ex_doc as an indirect dependency in Earmark so if you want to switch one day that would be great.

This PR just gives you the option and I'll try to sync it with upstream as much as I can

[wojtekmach]

LGTM!

Since we are not using many features from Earmark, depending on just the parser piece is definitely a win. I'm a little bit concerned that the split might generate more work for you (people will report issues in the "wrong" repo, syncing releases, etc) but hopefully these would be just growing pains and things will stabilise over long-term.

[RobertDober]

The split is risky and I might regret it, but I am a perfectionist and a risk taker.
I do not consider these traits being a quality but sometimes I just cannot hold back. (as they say above the Oracle of Delphi)

Ok enough psychoanalysis of an egocentric developer 😓 just as you might have noticed when upgrading Earmark beyond 1.4.7 you will use EarmarkParser anyway.

[RobertDober]

LGTM!

Since we are not using many features from Earmark, depending on just the parser piece is definitely a win. I'm a little bit concerned that the split might generate more work for you (people will report issues in the "wrong" repo, syncing releases, etc) but hopefully these would be just growing pains and things will stabilise over long-term.

Definitely it will remain a problem but I am prepared to deal with it. The release procedure will take more time too as the bulk of changes will be in the parser, I am just a mad man I guess ...

[eksperimental]

👏

[RobertDober]

This is really great for my dev circle. Thank you so much.