Clarify the scope of 'outside projects' that require prior approval

As originally phrased, without any scoping, 'outside projects' could reasonably be interpreted to cover personal plans/tasks/projects that are none of GitLab's business. This clarification seeks to limit the scope of the claim by explicitly stating what impact a possible project needs to have on GitLab before it requires approval, thus ensuring that there is limited chance for misinterpretation on either side. Some examples:

1. If I choose to undertake a multi-year build of a large model warship, that would be clearly a 'project'. However, if I only intend to spend an hour or two a week on it, as my spare time permits, there will be no impact on my ability to perform my duties for GitLab, and thus there should be no need to seek approval.
2. If I am planning on writing a large technical book that will be published in the near future, it is plausible that it could end up taking a lot of time/focus, but it will depend (amongst other things) on the planned timing/schedule. It may be necessary to seek approval in this case, but is not certain, and requires discretion.
3. If I'm wanting to create an entire new side business that will take me 10s of hours a week, then that would be clearly in scope for requiring approval (and could be denied).