linux: setup with new object system

[joshua-holmes]

• Setup Wayland to use new mach object system

  • In listeners, such as wl_registry_add_listener, rather than sharing a pointer to an instance of Linux with the Wayland server, pass the mach object system window id.
  • Store a pointer to Core in the global scope of Wayland so that listeners can use the provided window id and pointer to Core to lookup the data for that window, modify it, and save it directly in the handler function. See registryHandleGlobal() definition for an example.
  • Handle some errors that were previously unhandled
  • Handle getting and setting the state of windows when needed. Previously a step that wasn't done because we only had 1 state to manage, now we have 2: state in the local scope, and state in the mach object system (core.windows)

• Setup X11 to use new mach object system

  • Store native state in new Native struct
  • Store a pointer to Core in the global scope. I think this can be avoided. Not sure if it's a good idea for X11

• Setup logs to appropriately explain the current status of the X11 implementation, which is not functional

Both X11 and Wayland work at runtime

• By selecting this checkbox, I agree to license my contributions to this project under the license(s) described in the LICENSE file, and I have the right to do so or have received permission to do so by an employer or client I am producing work for whom has this right.

[joshua-holmes]

Started working on X11. Will probably just put it in this PR if it's not merged by then.

[joshua-holmes]

X11 now builds and runs

[joshua-holmes]

Setting title now works on both backends. It does this by checking if the window.title field has been updated every tick, if it has, update the window to reflect that.

[emidoots]

we should remove this function and inline this functionality where written