Split layrry-launcher module into embedded and cli

[moditect]

Split layrry-launcher module into embedded and cli

[aalmiray]

Hmm I guess it doesn't make much sense to have embeddable mode anyway.

[gunnarmorling]

You mean there's no point in having a public Layrry API, as it's going to be used most of the time configuration-based anyways? If so, I'm not sure I'd agree, I definitely see cases where you'd want to use the API. In any case not worth splitting into two modules IMO.

[aalmiray]

Well if API and CLI can be used separately then I'd still argue in favor of a module split because of publishing constraints. It makes sense for API to be a normal JAR while CLI is a shaded JAR.

It's true that a single POM can produce more than 1 binary but I rather keep the 1-to-1 mapping. Also, this way API takes no favorites on config impl (YAML, TOML, etc) while CLI does.

[gunnarmorling]

Ah, yes, fair point about the config dependencies.

[gunnarmorling]

Done.