[Ownership] Prevent ownership change on bootstrap comps

In nasa/mct#123 the user is able to change ownership
of My Sandbox, which means they subsequently cannot
edit their own sandbox. Worse, when they restart MCT
they see no sandbox at all.

This adds a check to prevent this. When ownership
mutability is being determined, consult the list
of bootstrap components - this is the list of
components seen by the user in the User Environment.
Categorically disallow changes of ownership to any
of these (this includes both My Sandbox, and any
future top-level components introduced, as these
are presumed to be inherently tied to the user. An
example of a top-level component not yet introduced
is User Tags, described in nasa/MCT-Plugins#39.)
[Ownership] Consider bootstrap comps in unit test

Consider the case of bootstrap components in
unit test verifying whether or not ownership
change to a component is allowed.
[Ownership] Fix unit tests

Amend unit tests to resolve issues related to
changes in support of nasa/mct#123.
Specifically:

* Change method annotations in RoleAccessTest
  to clean up on a per-method basis, avoiding
  interference with global state (platform)
  in other tests.
* Perform additional mock setup in test for
  info view, as platform is now indirectly
  consulted during the creation of that GUI.
Merge pull request #186 from VWoeltjen/mct123

[Ownership] Prevent changing owner of bootstrap components, such as My Sandbox