Support Campaign, Activation and Catalog in nondefault namespaces

[RemindD]

• enable campaigns, activations and catalogs to be created and workable in non-default namespace.

  • Enable CRUD of these objects in non-default namespace (already supported in b5e9664)
  • Enable reference of symphony objects outside of default namespace. Currently, we only allow reference within the same namespace. For example, if a campaign is created in namespace "n1", then only activations created in namespace "n1" can activate it. Below is a chart of reference of symphony objects.

	targets, instances, solutions	campaign	activations	catalogs
targets, instances, solutions	(already supported)			config reference (already supported)
campaigns	stage provider			stage provider
activations		1. trigger campaign 2. job report resume campaign
catalogs				parent site sync catalog to child

• Add namespace to in-memory objects

  • heartbeat of a job - job manager
  • success time of instance and target - job manager
  • summary - solution manager
  • record of how many child sites have completed remote jobs - stage manager

• Run campaign and activation integration tests in both default and nondefault namespaces

Tests:

1. Unit tests
2. Integration tests