Description of problem:
When applying some change that is org-specific (i.e., creating a new GPG key), it could appear out of context in the notification, like it is system wide. For org specific actions, we should append/prepend the notification somehow to indicate the org for which this action took place.

Obviously GPG is just an example. It should be a general design pattern that is applied to any org-specific action/notification.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.  Create a new org, "BACME_Corporation" with a third party provider and product
2.  In the original org (ACME), create a new GPG key called "Fedora 16"
3.  Switch to BACME_Corporation
4.  In BACME, create a new GPG key called "fedora 16"  
6.  Nav to the notifications view and/or Dashboard > Latest Notification.

Actual results:
"GPG Key 'fedora 16' was created." appears both times it is created.

Expected results:
Something like
[ACME_Corporation] GPG Key 'fedora 16' was created.
[BACME_Corporation] GPG Key 'fedora 16' was created.

Additional info:



< bbuckingham> cswiii, jrist, in the bz, rather than prepend text for the org, may be better to store the org in the model...  
< bbuckingham> in case org name were to change... or we wanted to do some searching based on notices for an org...etc