Fixes Terasology issue #998

This is intended to fix the following issue:
https://github.com/MovingBlocks/Terasology/issues/998

After a bit of investigation, the policy permission set seems to be modified by some part deep down in the RMI server used by JVisualVM to connect. The Policy base class will return an unmodifiable collection, which then leads to the witnessed Exception that bubbles up to JVisualVM via the RMI connection.

By simply returning a one-off collection that can be modified, the exception is avoided and the JVisualVM can successfully connect (and profile) Terasology.
Slightly off indentation here?