strategy for private moon-configs

[nhomble]

I am excited for this feature: https://moonrepo.dev/docs/guides/sharing-config

We enjoy moon as a tool to manage very large multi-module projects, but we still have use cases where it is desirable to have a couple of these repos rather than a single large one. In which case, we find certain moon tasks common across our repositories, so being able to extend from a common config is very desirable.

---

For users that will write custom tasks that don't make sense outside of their use cases, what are recommended strategies for sharing those configs? The examples from the moon docs only demonstrates public github user content which wouldn't work if we wanted to keep the custom tasks private.

[nhomble]

Related to #2164