[Fixes #104] Allow nested resources with the same name

[johanneswuerbach]

This PR allows nested resources to have the same name as the parent and doesn't overwrite their documentation by default. In the current version you have to set a custom resource_id, if the controller names were equal.

[iNecas]

Looks promising. However, this change is not useful for all the use-cases (see #77 (comment) for explanation of such a use-case). Making this as a configuration option would be great, letting the user decide the format of the resource identifier. What do you think?

[johanneswuerbach]

Sure, I'll update the PR.

[iNecas]

Fine, Please add that into into the README.rst as well to keep the documentation up-to-date

[johanneswuerbach]

I disabled the controller_paths by default to prevent breaking existing implementations, but I would recommend to enable it by default in a later version, because the default behaviour was quite confusing in the beginning.

[iNecas]

Great work! Merging. Next release planned for monday (I'm pushing some new stuff today as well). You're not the first one to pointing this out. I agree on turning this on by default once we turn the version to '0.1.0', it won't take long.