Fix for GH#6 - Create Step Definitions generates Reqnroll using State…

[clrudolphi]

…ments for SpecFlow projects Fixes Reqnroll.VisualStudio issue #6

Modified DefineStepsCommand.SaveAsStepDefinitionClass() to look for projectTraits.LegacySpecFlow or .SpecFlowCompatibility; if found use the SpecFlow namespace in the using statement.

I'm not quite sure how tests would be extended to cover this (or if it is even worth doing so).

• [X] Bug fix (non-breaking change which fixes an issue).
• [ ] New feature (non-breaking change which adds functionality).
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected).
• [ ] Performance improvement
• [ ] Refactoring (so no functional change)
• [ ] Other (docs, build config, etc)

Checklist:

• [ ] I've added tests for my code. (most of the time mandatory)
• [X] I have added an entry to the changelog. (mandatory)
• [ ] My change requires a change to the documentation.
• [ ] I have updated the documentation accordingly.

[gasparnagy]

@clrudolphi I have added you to the Reqnroll core-team group. This means that you can create PRs from branches of the main repo, without using and synchronizing your own fork. That model is anyway more convenient, because others can add extra commits to your PRs if you need that kind of help.