Fixed large and smallish memory leak

[MalekiRe]

From not destroying renderer. And not destroying wlr_surface.

[philpax]

It looks like the resources you're cleaning up in the destructor are pointers, so you can use a unique_ptr with a custom deleter: https://stackoverflow.com/questions/19053351/how-do-i-use-a-custom-deleter-with-a-stdunique-ptr-member

This saves you from implementing the destructor yourself, and maaaaay help in the case of partial initialisation (but don't quote me on that)

[technobaboo]

How can I ensure they all get destroyed in the right order @philpax?

[philpax]

The destruction order is in reverse order of declaration: https://stackoverflow.com/questions/29168162/destruction-order-of-class-data-members