If you want to store config files in a package, I found having separate packages for config and launch files is less problematic. Explained in a new section on a wiki page. Please review, and modify for any correction/improvement. I’m also happy to provide more context on this thread if desired.
Btw, spiting .launch and other config files into separate packages might go against some existing practices. E.g. A convention in ROS-Industrial suggests
*_support package to host launch and configs (which in fact is what I’ve been using and inspired my suggestion after I ran into some circular dependency issue).