Different behaviour for ambiguous steps in feature files and native tests

[ilyapuchka]

I noticed that there is currently different behavior when it comes to validating steps in NativeScenario and native tests. In native tests, there is no error because the first match is picked up, but in NativeScenario it results in ambiguity. Here is the example:

step("I'm logged in as (?!known)(.+)")
step("I'm logged in as (?<aKnownUser>Alice|Bob)")

// in feature file causes error
Given I'm logged in as Bob

// in native test - fine
Given("I'm logged in as Bob")

It is definitely possible to rewrite those two steps to avoid ambiguity but I think framework should behave the same way in both scenarios.