backends/drm: don't expose DrmPipeline state as a public member

While having all state be public is great for avoiding the boilerplate that comes with setters and getters, it also exposes more state than necessary to the rest of the backend and makes it more error-prone if more than one part of the state needs to be changed at the same time (which I need to do with output layers).