Explanation for energy_project_energy_communities module
With the last !210 (merged) MR the energy_project_energy_communities module only was used to add the groups to the roles declared in energy_communities.
The module energy_project_energy_communities was first added to not add a dependency in energy_communities with all the energy project related development. Now that doesn't make sense to our case because energy_communities is specifically a module developed to solve the specific cases of Som Comunitats project and needs the energy_project modules as it is in already in his dependencies (commit), so we can generate the demo data needed.
Explanation for energy_selfconsumption_cooperator module
Similar case, but so we don't generate a dependency between energy_selfconsumption and cooperator. We wanted to be able energy_selfconsumption to not depend on the coopeartor logic for the partners related, mostly in the inscriptions. But this added a lot of complexity with the last (commit) change, and it doesn't make sense to add complexity for a feature that we may not use. Still, we will document #38 all the dependencies uses to cooperator so if someone wants to remove it will be easier.
If we remove these modules, we remove the complexity related to the deployment and dependency structure of this project.
