Fixes unclean costmap2d shutdown

This change in the order of the declaration of subscriber and message filter resolves an issue we were seeing that caused costmap2d to crash or hang when shutting down.

The cause for the issue was that the message filter was being destructed first and then when the subscriber destructor kicked-in, it would try to unregister from the message filter which triggered a lock on a deleted mutex.

With this minor change now shutdown occurs in the proper order, subscriber is first unregistered when destructed and then the message filter can die and rest in peace.