fix the args passed to updateSchemaIfNecessary when adding a node

updateSchemaIfNecessary takes as args the previous and new cluster sizes. In
one of my recent commits, I was passing the wrong value for the previous size
when deploying a new node. It should not include the new storage node.
Fix issue with bundle unassign from group.
Bundle create wizard, xix issues with non-initial bundle version groups step
- also, remove asterisks from unassigned tree node
fix intentional api change issue
Fix nav issues resulting from cached views being unknowingly wiped
fix list view back button nav issue
Bundle create wizard, fix issue where "token" workflow generated an exception
in the message center.
remove view_bundles_in_group from the permission editor, it's implied and
should not be manipulated in the editor (like view_resources)
remove unwanted tooltip from bundle create wizard
Fix issue with bundle group removal from role.
bundle create wizard, Fix issue when there are no assignable groups
[BZ 995541] Remove JSF charting from Portal.war. More specifically, remove any java AWT references from classes which are the charting classes. Also make sure to preserve existing portal.war functionality such as content and timeline.
[BZ 999555] Add storage node password obfuscation in the server configuration file using the same method applied to SQL database password.

Also, added a more generic argument to the installer to allow users to encode their desired password prior to running the installer.
Fix file paths for running the schema manager from a disk based distribution.
Bug 791340 - Exploded WAR deployed through JON never added to inventory

When a new resource deployment takes some time, the CreateResourceRunner won't be able to discover the new resource. Eventually, the user will have to wait for next automatic service scan to see the resource in the inventory, or will have to trigger a service scan manually.

Now CreateResourceRunner will try up to five times to detect the new resource, with a 30 seconds pause between tries. That gives the managed server up to 5 minutes to deploy it.
Fix issue with perm check in get assignable bundles
- Fix some error handling workflows
- Complete I18N support
Shutdown the cluster manager if the session connection fails; otherwise various mananger specific connections could remain open.
Properly close Cassandra cluster sessions in the rest of the code (schema manager, storage cluster client manager bean, data migrator).
Refactor log variable name.