add cachelookup annotation support

[groov1kk]

Proposed changes

Added support of @CachedLookup selenium annotation for page objects:

public class SelectsPage {

    @CacheLookup
    @FindBy(xpath = "//select[@name='domain']")
    WebElement domainSelect;

    @CacheLookup
    @FindBy(tagName = "h1")
    SelenideElement h1;

    @CacheLookup
    @FindBy(tagName = "h2")
    List<SelenideElement> h2s;

    @CacheLookup
    @FindBy(tagName = "h2")
    ElementsCollection h2sElementsCollection;

    @CacheLookup
    @FindBy(id = "status")
    StatusBlock status;

    @CacheLookup
    @FindBy(css = "#user-table tbody tr")
    List<UserInfo> userInfoList;

  }

Checklist

• Checkstyle and unit tests are passed locally with my changes by running gradlew check chrome_headless firefox_headless command
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)

[asolntsev]

Hi @groov1kk !
I like how you implemented this feature. A deep understanding of the existing code base. Nice!

I have only two concerns:

1. Is it really needed? Did you have a chance to measure how many seconds will this feature save?
   When I measured it last time, the gain for so small that I decided element caching is not worth the effort. It gave so few seconds... Most of the times, the slowness comes from browser, backend, services etc., but not from finding the web elements.
2. If we decide it's needed, it would be also great to implement caching of elements in the "standard" methods $ and $$. But what would be the API? Should it be a global setting, or an additional parameter in overloaded $/$$ method?

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[groov1kk]

Hello

1. From my experience, I received benefit from this feature when I worked with complex static structures such as tables, in cases when I was needed to iterate through many rows and cells to find desired element. In such structures you couldn't collect all elements using single findElements request and have to make additional sub-finds. And, for example, I had to iterate through this structure several times in one test. But yes, it wasn't significant improvement, something about 5-15 seconds. Anyway, pure selenium has this feature and I just have a habbit to mark all static content with this annotation just not to make additional useless requests :)
2. I thought about this. It shouldn't be a global feature because usually we have to work both with static and dynamic elements. Developer must decide how to work with elements on the spot. So, either we can overload existing methods ($(cssSelector, shouldCache), etc) or create different methods (cache(seleniumSelector), cacheAll(cssSelector), xCache(xpathSelector), etc)

[asolntsev]

Seems a very well done PR to me.
Thumbs up! @groov1kk