output_get_active_workspace: check workspaces length
output_get_active_workspace: check workspaces length

If an output's node was dirty and the transaction was committed before a
workspace was moved to or created for the output, the instruction would
have a bad value for `state->active_workspace` due to a missing
length check in `output_get_active_workspace`. If there was no focus on
the output, the first workspace was being returned. If the workspace
list was currently empty, the value was either garbage, or in the case of
an output being disabled and re-enabled, a workspace that may have been
previously freed. This just adds the length check to avoid returning out
of bounds value.

1ace/sway,ascent12/sway,1ace/sway,1ace/sway,ascent12/sway,SirCmpwn/sway,ascent12/sway