Refactoring: Abstracting the BDD parts out to a shared package

[eduncan911]

In order to support a number of new features, I will need to represent the core BDD principals in code.

I do not want to pollute the root mspec package. Instead, I would prefer to abstract, create and move the core BDD parts out to a dedicated package. Most likely:

github.com/eduncan911/mspec/bdd

This could have some nice side effects, besides supporting other code and runtimes I plan on building. For example, someone could import that package directly and use it to create their own test runner, web-driven BDD framework, etc.

See #4 for details.

[ddspog]

@eduncan911 Are you still working on this package refactoring?

[eduncan911]

@ddspog it has taken a backseat to some other projects.

looks like i haven't checked in the progress so far. it's far from usable though.

In short, the API does remain the same with no breaking changes (so far). It just adds more functionality and options.