Fix wrong boundary ID assignment

The convention in Arepo appears to be this way around, which can cause a lot of
confusion. This will be overridden by the refactoring of the ID assignment
logic but the hotfix is still necessary.
Update MD5 hash in test
Merge pull request #51 from aepsil0n/fix/boundary_ids

Fix wrong boundary ID assignment