Support Bazel workspaces that have packages with same name in different paths

[plaird]

As a BEF user with a particular Bazel workspace
I would like to import the workspace entirely
Such that there is a way to handle multiple Bazel packages with the same leaf path name

Example:
Consider a Bazel workspace with this structure:

//projects/path1/apple-api/BUILD (java_library target here)
//projects/path2/apple-api/BUILD (java_library target here)

Right now you cannot import the entire workspace, you have to choose to only import one of the apple-api packages. This is because we name the Eclipse project with the leaf node of the path (apple-api). An Eclipse workspace cannot contain two projects of the same name.

[plaird]

Initial implementation should just tack on a numeric on the end of package name as needed. In the above example, the two projects would get named:

• apple-api
• apple-api2

without regard to the path names. So apple-api2 may be the project for package //projects/path1/apple-api/

But eventually I would like to support user configuration of the chosen project names using inline annotations in the BUILD files: see #177