Fort: a few minor bug fixes, primarily namespacing
Legacy Content View: quick fix to address issue on publish

This commit is just a 'quick fix' to address an error that can
occur on publish due to double form submits.

Note; this is only temporary as we replacing this UI in the
cv-rework branch.
add rubygem-hammer_cli_foreman_tasks to repos
subscriptions - manifest refresh and delete into dynflow actions
fixes #4505 - rhsm register though Dynflow
Merge pull request #3761 from iNecas/update-consumer-create

fixes #4505 - rhsm register though Dynflow
Merge pull request #3755 from bbuckingham/bugfixes

Bugfixes for legacy content view publish
Merge pull request #3756 from jmontleon/add_hammer_cli_foreman_tasks_to_repo

add rubygem-hammer_cli_foreman_tasks to repos
fixes #4409 - rename the id used for the content menu

For some reason, using 'content' as the id for the Content menu
was resulting in breakage in behavior for foreman's two-pane
implementation.

Without this change, the following would occur:
- User goes to a page, clicks 'New <object>' (e.g.
  Architecture, Environment, User...)
- panel opens with form to allow user to enter
  data for the object
- User clicks submit
- At this point, the form is submitted to the server
  and the object is created; however, the form is never
  closed and the list of objects is not updated.
Merge pull request #3760 from komidore64/manifest-async-tasks

subscriptions - manifest refresh and delete into dynflow actions
Merge pull request #3769 from bbuckingham/issue-4409

fixes #4409 - rename the id used for the content menu
Code for Org  Create orchestration