N1QL plan analyzer cannot select an index if a list is given in parameters

Problem:

When using a list parameter value for N1QL query with IN statement - it fails to properly build an index scan.  As a result performance is hit dramatically for large data sets.

This issue is not observed if using a hand-made query where a list parameter was inserted manually.

Steps to Reproduce:

1. Install travel-sample bucket.
2. Run attached screen.
3. Compare Explain output and timing.

Expected Result:

Both queries (with parameters and without parameters) are semantically the same, hence both explain and time to run a query should be the same.

Actual Result:

A plan analyzer fails to properly build an index scan for a parametrized query.
As result a time to run it is much higher: it's 2s vs 300ms for a travel-sample; in our real-world scenario with 1M records it is like 2 minutes vs 2-3 seconds.