Remote roles surfaces still using activation by default

Close for Pike M1

Yeah, I've added that before actually looking into the matter more closely. Thanks!

@Marius Vlad Thanks for the explanation. I edited the description to remove the reference to getting this into Octopus. 

If I were to cherry-pick this back I need to bring all the bits have landed into master as well. Unfortunately I don't have a easy way to backport it. Reason being we depend on some protocol update which also include some other stuff we don't need, and for that I need be careful with forward compatibility which would be a nightmare to resolve.

For this to work out correctly, the client needs some additional information, which is provided by that protocol update. Together, both the shell client and the compositor would choose the output, rather than letting that to the compositor. So it works just fine as is, even though the ini configuration would say otherwise. That's the caveat, the compositor will silently ignore implicit activation for this surface roles (for octopus).

In master. we removed that implicit activation entirely, and it now obeys the ini configuration file. But like I've said above, this now works in-tandem with the shell client.

@Jan-Simon Moeller or @Marius Vlad  Please cherry pick for Octopus