Workaround to fix the path of moved objects

[ale-rt]

This PR wants to provide a workaround for the issue described in plone/plone.api#430.
The reason why this PR is needed is that moving an object does not actually updates the object stored in the intid persistent utility because the relevant BTrees do not recognize that the key is changed (probably because the computed __hash__ does not change).

Closes plone/plone.api#430

[mister-roboto]

@ale-rt thanks for creating this Pull Request and help improve Plone!

To ensure that these changes do not break other parts of Plone, the Plone test suite matrix needs to pass.

Whenever you feel that the pull request is ready to be tested, either start all jenkins jobs pull requests by yourself, or simply add a comment in this pull request stating:

@jenkins-plone-org please run jobs

With this simple comment all the jobs will be started automatically.

Happy hacking!

[ale-rt]

@jenkins-plone-org please run jobs

[ale-rt]

@plone/release-team is it possible to activate the issue tracker? There are other issues that I think should be checked in this package:

• KeyReferenceToPersistent.__hash__ should be checked (See KeyReferenceToPersistent.__hash__ should be checked #9)
• KeyReferenceToPersistent.__cmp__ should be replaced by KeyReferenceToPersistent.__eq__ + KeyReferenceToPersistent.__lt__ + @functools.total_ordering to properly working on Python 3. (See KeyReferenceToPersistent.__cmp__ should be replaced #10)
• Should we store objects in the intid utility? I suspect storing the object is not needed and might cause issues on migrations (because of classes that might be missing). (See Check if we can avoid storing objects in the intid utility #11)

[gforcada]

@ale-rt issues enabled, feel free to create new issues 👍

[ale-rt]

Thanks @gforcada!