Remove references to the Chisel package in favor of explicit chisel3 imports in tests,

Import chisel3.NotStrict.CompileOptions in Chisel package.
Add CompileOptions tests.

Stricter values are "true". Current default (not strict) values are "false".

Public APIs for chisel object names

Use bulkConnect in Vec,fill if any (flattened) element of the Vec has a direction associated with it.
This impetus for this came out of discussion during the chisel meeting of 8/24/16 in response to errors running the chisel tutorial examples Adder test.

signalName -> instanceName
SignalId -> InstanceId
Based on Stephen's comments on PR

Removed extraneous logic
Renamed doStuff to buildAnnotatedCircuit
Removed println's

Add AnnotationSpec file which provides an example of a way to implement generation of annotations in a chisel circuit that could be used by custom firrtl passes
This spec also shows and tests in a limited way the new API of .signalName, .pathName, parentModName which allows access to the various path information of a chisel component (something that subclasses SignalId, most prominently SubClasses of Data and Module

* signalName: returns the chirrtl name of the signal

* pathName: returns the full path name of the signal from the top module

* parentPathName: returns the full path of the signal's parent module instance from the top module

* parentModName: returns the signal's parent **module(not instance)** name.

Input, Output, and Flipped clone their inputs.

As a side-effect, handle BlackBoxes correctly.

Revive support for firrtl flip direction.
Remove compileOptions.internalConnectionToInputOk

Assume LHSItOutput if neither side is driving.
Restore Wire()'s removal of direction in binding.

* Make "def width" a private API; expose isWidthKnown instead

Resolves #256.

Since width was used to determine whether getWidth would succeed, I added

    def isWidthKnown: Boolean

but another option would be to expose something like

    def widthOption: Option[Int]

...thoughts?

* Document getWidth/isWidthKnown

* Add widthOption for more idiomatic Scala manipulation of widths

Nothing uses these now, but when we integrate Stephen's PR200, we'll need a way to selectively enable some strict connection checks on a file by file basis. We plan to do this using package imports which will define suitable compilation options.

The API allowed this before, but not safely, as users could create
name conflicts.  This exposes the pre-deduplication/sanitization
naming API, and closes the other one.