BasicComponentFinder fails immediately without timeout when no match found

Currently the BasicComponentFinder fails immediately if no match is found. In many situations it would help that it tired to find for specified time before failing. This would make tests more robust.

Locate BasicComponentFinder and the existing path that fails when no match is found. Read the related tests, then determine how a specified search duration should be supplied and verified; done means it waits for that duration before failing and the tests cover the delayed failure behavior.

Written by the indexing model from the issue text.