Add pipelineScheduleUpdate mutation

What does this MR do and why?

• Added pipelineScheduleUpdate mutation
• Added PipelineSchedulVariableInput Type
• Added PipelineSchedule GraphQL Type
• Added PipelineScheduleVariable GraphQL Type

mutation PipelineScheduleUpdate($input: PipelineScheduleUpdateInput!) {
  pipelineScheduleUpdate(input: $input) {
    errors # [String]: Array of error messages, empty if it's successful.
    pipelineSchedule {
      active
      cron
      cronTimezone
      description
      id
      owner {
        publicEmail
      }
      project {
        path
      }
      ref
      variables {
        id
        key
        raw
      }
    }
  }
}

input PipelineScheduleUpdateInput {
  """
  Indicates if the pipeline schedule is active or not.
  """
  active: Boolean

  """
  A unique identifier for the client performing the mutation.
  """
  clientMutationId: String

  """
  Cron expression of the pipeline schedule.
  """
  cron: String

  """
  Cron timezone of the pipeline schedule.
  """
  cronTimezone: String

  """
  Description of the pipeline schedule.
  """
  description: String

  """
  ID of the pipeline schedule to mutate.
  """
  id: CiPipelineScheduleID!

  """
  Ref of the pipeline schedule.
  """
  ref: String

  """
  Variables for the pipeline schedule.
  """
  variables: [PipelineScheduleVariableInput!]
}

input PipelineScheduleVariableInput {
  """
  Name of the variable.
  """
  key: String!

  """
  Value of the variable.
  """
  value: String!

  """
  .
  """
  variableType: CiVariableType
}


enum CiVariableType {
  ENV_VAR
  FILE
}

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.

Related to #372129 (closed)