Unfortunately there are a few job parameters that have default values that differ when no value is specified vs an empty value is specified. For example: `rules` and `needs` behave differently if not specified at all vs an empty array `[]`. The yaml file format suggests that a `null` might be want we want to "unset" the value, but this does not work to clear Component inputs. See: https://gitlab.com/gitlab-org/gitlab/-/issues/439524.
Unfortunately there are a few job parameters that have default values that differ when no value is specified vs an empty value is specified. For example: `rules` and `needs` behave differently if not specified at all vs an empty array `[]`. The yaml file format suggests that a `null` might be want we want to "unset" the value, but this does not work to clear Component inputs. See: https://gitlab.com/gitlab-org/gitlab/-/issues/439524. In the case of `rules`, you can use `[{when: on_success}]` to force the default behavior as if no rules were provided. This isn't the case with `needs` though - you can't clear it.
