feat(esl-media-query): ingore tuple values if query syntax passed

[fshovchko]

Closes: #2377

[ala-n]

$${\color{red} NOT ACTUAL }$$

The only open questions (for voting I guess) is the new method name and signature.

For the context:
The new method is used to parse query according to its syntax and based on user input so both
parse ('1 | 2 | 3', TUPPLE_MEDIA) and parse('@XS => 1 | @SM => 2 | @MD => 3', TUPPLE_MEDIA) (TUPPLE_MEDIA provided but not used in that case) will be handled correctly.

The purpose of creating this method appeared

• from the real project (where tupple with global media preset is used with potential usage of extended arrow syntax)
• and in purpose to extend carousel API

    <esl-carousel media="@XS | @SM | @MD" count="1 | 2 | 3" ...>
    vs
    <esl-carousel count="1 | @SM => 2 | @MD => 3" ...>
  

Three is an existing method parse presented in ESLMediaRuleList but it can not be used to parse query in the mentioned way due to arguments order (array syntax and tupple media are the first arguments so it is mixed and depends on argument count)

1. So first of all we need a clear name for new method:
   g. flexibleParse 0 1.5 1.5 1 0 1.5 5.5
   k. parseMixed 1.5 0 0 1.5 1.5 2 3 9.5
   b. addaptiveParse 1.5 1.5 1.5 1.5 1.5 0 1.5 9

   parseAny
parseAuto

   a. parseAdaptive 0 0 0 1

   c. autoparse 0 0 0
   d. autoParse 0
   f. parseFlexible 0

   l. parseMixedValue 0

2. The signature of the method is also a little bit questionable.
   I'd suggest to restrict it to

parseAdaptive(value: string, mask: string): ESLMediaRuleList;  
parseAdaptive<U>(value: string, mask: string, parser: RulePayloadParser<U>): ESLMediaRuleList<U>;  

We have a "low level" parse which accepts any argument count depending on what we are going to parse.
The new method's purpose is always to parse uncertain user input, so providing media tuple is mandatory in that case.

Please make me know if there is a concern with that point

FYI: @exadel-inc/esl-all-contributors

[codeclimate]

The PR diff size of 13962 lines exceeds the maximum allowed for the inline comments feature.

[codeclimate]

Code Climate has analyzed commit 438c1a9 and detected 4 issues on this pull request.

Here's the issue category breakdown:

Category	Count
Complexity	2
Duplication	2

The test coverage on the diff in this pull request is 61.1% (50% is the threshold).

This pull request will bring the total coverage in the repository to 64.7% (-0.5% change).

View more on Code Climate.

[ala-n]

🎉 This issue has been resolved in version 5.0.0-beta.25 🎉

The release is available on:

• npm package (@beta dist-tag)
• GitHub release

Your semantic-release bot 📦🚀