Link HTTP config requests to their provider modules

I added a calculateDependencies() function to the config request entity. This adds a module config dependency every time a new one is created or updated.

I briefly explored creating a hook_update_n to make this change for all existing HTTP config requests, but I wasn't sure what the best practice is for config entities. I think the typical workflow of importing config in production, then running database updates wouldn't be compatible with this. It would be nice to update existing config entites, and if you know what the correct method of doing it would be, I'll make it happen. But otherwise, I'll say it's a nice to have and not required.

Hi and thank you again for your contribution @rocketeerbkw.
Patch applied :)

Regards,
aronne

Automatically closed - issue fixed for 2 weeks with no activity.