CE-3179: Add configuration for lab deployment server

Configuration for lab deployment server. Some questions:

• Can we use the same ccce_gitlab_technical_user_token? This has write access to gitlab for a certain group, which I think is still correct in this case.
• What about the inventory to use? It seems we either could have a custom cslab inventory, but we could also limit the hosts using the job template. (See CE-3178)
• Do we need a new awx token? What about the database password?
• What about ccce_awx_suffix? This seems only to be used for the notification template. Come to think of it, do we actually use the notification template? Wasn't this just used for providing a notification back to ce-deploy? @imretoth

@andersharrisson , some input on a few of these would be appreciated, in particular about the best way to handle the inventory question.

Edit: Remaining questions:

• Tokens/passwords
• • ccce_gitlab_technical_user_token: this is used to read from gitlab and create iocs in the manual group; this can likely stay.
• • ccce_awx_token: This is how the BE triggers actions on AWX; this can presumably stay the same
• • ce_deploy_database_password: This is just the password used from the BE to the DB container. I guess it can stay, although it does mean we are re-using a password. Probably no one cares.
• ccce_awx_suffix: Just in use for notification templates. We can leave this be but might want to revisit this later.