When we include a submodule (which is in another file) into module
then generated ResourceYangModuleInfo#resourceName returns instead of
the submodule's resource file name the resource file name of the module
in which the submodule is included.

This can lead to SchemaResolutionException beacause of unsatified
imports during assembling of EffectiveModelContext and thus
to application failure during start.

The behavior has changed (the bug is present) in Silicon (7.0.x branch),
please see attached Gerrit reviews.