Add DAST Profile Schedule to Profile Type Query

What does this MR do?

Parent MR: !68046 (merged)

Child MR: !66445 (merged)

Profile Schedule Query now can be used to fetch DAST Profile Schedule.

Notes

The sequence of Merge, we will start from merging top MR to the master:

1. !68031 (merged) -> Scheduling logic and DB changes
2. !68046 (merged) -> dastProfileCreate mutation
3. !68050 (merged) -> dastProfile fetch Query
4. !66445 (merged) -> dastProfileUpdate mutation

Queries for testing:

Fetch Profile Schedule query

Click to expand

query DastProfiles($fullPath: ID!, $after: String, $before: String, $first: Int, $last: Int) {
  project(fullPath: $fullPath) {
    dastProfiles(after: $after, before: $before, first: $first, last: $last) {
      pageInfo {
        ...PageInfo
        __typename
      }
      edges {
        node {
          id
          name
          dastSiteProfile {
            id
            targetUrl
            __typename
          }
          dastScannerProfile {
            id
            scanType
            __typename
          }
          dastProfileSchedule {
            id
            active
            startsAt
            timezone
            nextRunAt
            cadence {
              duration,
              unit
            }
          }
          branch {
            name
            exists
            __typename
          }
          editPath
          __typename
        }
        __typename
      }
      __typename
    }
    __typename
  }
}

fragment PageInfo on PageInfo {
  hasNextPage
  hasPreviousPage
  startCursor
  endCursor
  __typename
}

{"fullPath": "root/dast-test", "first": 10 }

Screenshots or Screencasts (strongly suggested)

How to setup and validate locally (strongly suggested)

Does this MR meet the acceptance criteria?

Conformity

• I have included changelog trailers, or none are needed. (Does this MR need a changelog?)
• I have added/updated documentation, or it's not needed. (Is documentation required?)
• I have properly separated EE content from FOSS, or this MR is FOSS only. (Where should EE code go?)
• I have added information for database reviewers in the MR description, or it's not needed. (Does this MR have database related changes?)
• I have self-reviewed this MR per code review guidelines.
• This MR does not harm performance, or I have asked a reviewer to help assess the performance impact. (Merge request performance guidelines)
• I have followed the style guides.
• This change is backwards compatible across updates, or this does not apply.

Availability and Testing

• I have added/updated tests following the Testing Guide, or it's not needed. (Consider all test levels. See the Test Planning Process.)
• I have tested this MR in all supported browsers, or it's not needed.
• I have informed the Infrastructure department of a default or new setting change per definition of done, or it's not needed.

Security

Does this MR contain changes to processing or storing of credentials or tokens, authorization and authentication methods or other items described in the security review guidelines? If not, then delete this Security section.

• Label as security and @ mention @gitlab-com/gl-security/appsec
• The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
• Security reports checked/validated by a reviewer from the AppSec team

Related to #330308 (closed)