dependencies are not changed after a rename

[mzarnowski]

[propensive]

@marek1840 I've slightly changed the scope of this ticket to include updating dependencies too. Just letting you know in case that has an impact on #226.

[mzarnowski]

Indeed it does, since #226 closes the previous formulation of this issue and new formulation extends the scope, maybe it would be better to create new ticket instead? More so, since schema and dependencies not being updated after a rename - while similar in nature - require changes in very different parts of fury

[propensive]

Some work has been done to update the main project when the name of the current project changes, but renaming modules and schemas has not been fixed yet.

In the case of renaming dependencies, I believe that this should be applied very selectively. If a module or project is renamed, dependencies from other modules in the same layer should be renamed. This needs to be applied very carefully when the rename applies to multiple schemas, because they may differ in their dependencies. The rename process should be applied independently for each schema.

We cannot update dependencies in other layers, and users should be warned that this is the case.