Fixing issue #40 SG Name Collisions

Security Monkey was unaware that security group names in different VPC's
could collide.  Security group names in EC2 may also collide with a VPC
security group name.  The fix is to include the security group ID and
optionally the VPC ID to the name stored by security_monkey.
Merge branch 'hotfix/issue_40_security_group_name_collision'