Unexpected Range Behaviors

There are two main issues being reported here:

1. Strict mode vs not does not give the same behavior in simple ranges, where strict mode works and lax does not. In this example, there are extra spaces in the range.

    assert_equal '12345',
     Liquid::Template.parse('{%for item in (1 .. 5)%}{{item}}{%endfor%}').render

2. Both strict and lax mode do not support range in a variable outside of for loop. This works in LiquidJs and DotLiquid

assert_equal '12345',
     Liquid::Template.parse('{{(1..5)}}', error_mode: :strict).render

3. Variables with double dots trip the regex method of parsing ranges

  def test_range_dotted_variable
    nativedata = { 'paths' => { '..' => 1, '...' => 5 } }
    assert_equal '1 5',
     Liquid::Template.parse('{{ paths[".."] }} {{ paths["..."] }}', error_mode: :strict).render(nativedata)
    assert_equal '12345',
      Liquid::Template.parse('{%for item in (1..paths["..."]) %}{{item}}{%endfor%}', error_mode: :strict).render(nativedata)
    assert_equal '12345',
      Liquid::Template.parse('{%for item in (paths[".."]..paths["..."]) %}{{item}}{%endfor%}', error_mode: :strict).render(nativedata)
  end

Start by reproducing the three examples through Liquid::Template.parse, comparing strict and lax modes and range expressions inside and outside for loops. Trace the range parsing and variable lookup entry points implicated by those examples; done means all shown assertions produce the expected output without breaking dotted variable names.