Range parsing is not RFC 7950 compliant

[loeliger]

A leaf node with a range like this:

leaf thing {
    type uint8 {
	range "7 .. 17";
    }
}

fails to parse properly even though it is RFC-7950 compliant.
The RFC says:

;; Ranges

   range-arg-str       = < a string that matches the rule >
                         < range-arg >

   range-arg           = range-part *(optsep "|" optsep range-part)

   range-part          = range-boundary
                         [optsep ".." optsep range-boundary]

   range-boundary      = min-keyword / max-keyword /
                         integer-value / decimal-value

    optsep              = *(WSP / line-break)

   WSP                 = SP / HTAB
                         ; whitespace

I think clixon needs to relax its parsing an allow white spaces
around the three range tokens.

[olofhagsand]

This should have been fixed recently in develop, see:
c7e847c
Did you see this on master or on an earlier develop checkout?

[olofhagsand]

This should work

[olofhagsand]

Reopening. still broken.

[olofhagsand]

Fixed (again)