Module is creating the wrong settings file YML in config and unable to be imported

Problem/Motivation

After installing this module through composer and drush and doing a configuration export the module creates a "media_webdam.settings.yml" file in config.

Upon first inspection of the code with a Ctrl+F, I am unable to locate a mention in the module to media_webdam.settings, so I'm not sure why this is happening exactly but it has happened for myself and also a fellow dev working on this project and caused our Ci to fail on import and also local development.

ALSO:
If you uninstall the module via UI or Drush, that settings file just stays in your configuration files and does not delete itself or remove when config is exported after uninstallation.

Steps to reproduce

- Install and enable module
- Export Config, see file gets created
- Uninstall the module (see file stays)
- Try to import the configuration, (You should get the import fail message).

My manual resolution/workaround

When I manually rename the config settings file webdam.settings, export the config, it deletes the table from my database and the module continues to function as it is correctly installed. However I haven't saved any config settings to it just yet to confirm, but I was able to import the config again on a separate instance without a failure.

Although this has a manual workaround, it seems like a hugely detrimental issue for this module's use and should probably be addressed in the near future.