Allow changing ingress rules after security group creation

* Updated the acceptance test to check both that rules are added
* and that rules are deleted
So after looking at the Jenkins failure message (which is in a different spot than the new acceptance test I added), I think AWS is actually ordering things in a stable fashion.  I think the issue is that in CI, the temporal naming is a bit different from what we see locally, and due to this, we've exposed a divergence between Ruby's default alphanumeric sort and the AWS sort.  The particular failing case had the names of sgs sorted differently for:

```
0.0.1-b20073-stage80061939-8a56bc9f-6b6e-42a2-8074-d383b977fab8
0.0.1-b20073-stage80061939-07776d6a-8349-4808-8922-f3d36054646d
```

It was still sorting the protocol / port expectedly based on what I added to the acceptance test.

So I'm not sure if the best approach here is to match the sorting on both sides of the equation like you've done... or to fix `order_ingress` so that when sorting on name, it matches what AWS does.  I could see a case made for both approaches, though what you've done here is definitely the easier (but slower) way.  FWIW, I did a quick search and couldn't find any info on how exactly AWS sorts - and given it's not documented that probably means they're free to change it whenever they want.  So with that said, I would lean toward what you've done in this commit.

That said, we should adjust the commit message because it's misleading - I don't think that AWS is operating willy nilly here -- it's just that our sort algorithms don't necessarily match.