This creates the following four subdirectories:

* `frontend/`, which is for user-visible libraries exported by
  `lib/unittest.dart`.

* `backend/`, which is for libraries that define the internal
  structure of test suites and how they're run in a platform-
  independent manner.

* `runner/`, which is for libraries that are specifically useful for
  the test runner. This includes code that deals with multiple test
  suites at once as well as platform-specific test running code.

* `util/`, which contains various utility libraries that aren't
  specific to unittest's use-case. Individual utility functions can
  still go in `lib/util.dart`.

* `deprecated/`, which contains deprecated libraries.

R=kevmoo@google.com

Review URL: https://codereview.chromium.org//955543002

This preserves the shape of the previous API, but stubs out the functionality.
This is a temporary measure designed to make it easier for users to try the
runner out on their existing tests.

R=kevmoo@google.com
Closes #2

Review URL: https://codereview.chromium.org//934413002

This is still extremely bare-bones and won't work with tests that actually
import "package:unittest/unittest.dart", but it's something.

R=kevmoo@google.com
See #2

Review URL: https://codereview.chromium.org//933083002

This fixes tests that don't require dart:io and marks those that do
dart:io as Skip.

R=kevmoo@google.com

Review URL: https://codereview.chromium.org//918853005

R=kevmoo@google.com
See #2

Review URL: https://codereview.chromium.org//920703006