Allowing mkdocs-monorepo.yml to integrate existing mkdocs site without breaking configuration

Thank you for making this useful tool. I have one suggestion.

I can't seem to be able to use any file name other than mkdocs.yml. Can you allow the existing site to use the mkdocs.yml file, and use a different configuration file when connecting to monorepo?

This will allow for a more various configuration and will be useful.

Locate the configuration-loading entry point and trace how mkdocs.yml and mkdocs-monorepo.yml are handled. Confirm how an existing site can retain mkdocs.yml while the monorepo integration uses a separate configuration file, without breaking either configuration.

Written by the indexing model from the issue text.