teach cmp matcher octal tricks

[srenatus]

This addresses #230. The underlying problem is that as far as I can tell no way to figure out if an Integer argument to a matcher was given in using octal literals (0777) or not (511). To work around this, this change lets you use the cmp matcher for octal strings, for example:

its('mode') { should eq 0766 }
its('mode') { should cmq '0766' }

will give you (on a file that has permissions 0765):

Failures:

  1) File /tmp/file mode should eq 502
     Failure/Error: DEFAULT_FAILURE_NOTIFIER = lambda { |failure, _opts| raise failure }

       expected: 502
            got: 501

       (compared using ==)
     # ./test/integration/default/file_spec.rb:41:in `block (2 levels) in load'

  2) File /tmp/file mode should cmp "0766"
     Failure/Error: DEFAULT_FAILURE_NOTIFIER = lambda { |failure, _opts| raise failure }

       expected: 0766
            got: 0765

       (compared using `cmp` matcher)
     # ./test/integration/default/file_spec.rb:43:in `block (2 levels) in load'

Note that aruba is solving the issue differently: they introduced a matcher for that. It's up for debate, I slightly prefer the cmp matcher.

[chef-supermarket]

Hi. Your friendly Curry bot here. Just letting you know that all commit authors have become authorized to contribute. I have added the "Signed CLA" label to this issue so it can easily be found in the future.

[srenatus]

🔧 note that the leading 0 is mandatory. its('mode') { should cmp '765'} will fail.

[chris-rock]

Great work. Thanks @srenatus