Dyamic max results

[t9md]

Description of the Change

@jarle , @nathansobo How you think this?

This is proof of concept to solve #80.

Approach taken in this PR is different from #94
So changes done in #94 is intentionally reverted to re-think problem clearly again.

• This PR is not finished, Test is broken, just wanted to show different idea to tackle initial-open lag issue.
• I thinks this "dynamic truncation/un-truncation to reduce items to attache to DOM" feature can be implemented in atom-select-list rather than command-palette.
• But works as expected in UX-wise(faster initial open response time).
• console.log is not removed so that other people can easily correlate following GIF to code.

Alternate Designs

#94

Benefits

Stupidly simple.

Possible Drawbacks

When user mouseover, first core:move-down(down arrow key), it cause full item rendering.
So user experience lag at this timing.
But this is acceptable drawbacks since experience lag occasionally is far better than experience it always.

Applicable Issues

#80.

[nathansobo]

Still seems like the ideal approach would be to only render items as they become visible, but if this solves our immediate issue then if someone can get it green, I say we can proceed with it.

[t9md]

Thanks, I will do.
Also try with better implementation.

Provides dynamic rendering when it become visible by atom-select-list is best solution.
Maybe enable it by passing dynamicRendering option to avoid breaking specs for other select-list using pkg..
Will see...

[t9md]

Close in favor of #101