Precise Gitlab environment usage

Since !101 (merged), there are some rare case where delayed 'wait' job refuse to start.

Looking closely to the Gitlab documentation makes me identify that when an environment is attached to a job, the default action is 'start'. Maybe concurrent 'start' job can prevent some older action to be run as expected. The MR tries to overcome these issue by setting action to access in order to hopefully allow smoother concurrent operations.