Refs #20045; attempt to find a relationship by looking backword in the interfaces that the object provides if there is no forward relationship found with the default sorting
Refs #20045; fixed check for forward_relations that broke badrelations test
Refs #20045; WIP adding test that describes the changed behaviour when a relationship content type is discovered by the connector when it doesn't have a forward relationship with a given object which was added from a more generic relationship
Refs #20045; added needed newline to categorizations.txt in order to fix those tests
Refs #20045; modified forward logic in order to be able to pass a parameter in order to make an extended search which will search all of the interfaces for matches of relation contenttypes which will be checked for possible relations
Refs #20045; Changed the following:

- Renamed the parameter to perform the extended search deep_search
- Updated functional test documentation better explaining how the
  deep_search parameter is affecting the relationship discovery output
Refs #20045; pass deep_search option also to forward_backward method from macro.py which is responsible for the relations display from the relations viewlet
Refs #20045; fixed relation for categorizations.txt forward relation test
Refs #20045; removed stub method from __init__.py of component package and removed length check since without passing deep_search queryContentType would return only 1 result
Refs #20045; reverted logic of relationship discovery to the logic done in commit f2b099; since the latest commits made the forward relationship return multiple values which was not something that backward relationship lookup was modified to do
Refs #20045; added history entry for the major changes done within this ticket regarding forward relationship discovery
Merge pull request #3 from collective/relation_discovery

Forward Relation discovery