Create DastSiteProfile from GraphQL mutation

What does this MR do?

hooks models created in !36659 (merged) to existing services in order to create dast_site_profiles and dast_sites in the db. this merge forms part of the work that iterates on the existing dast on-demand functionality.

How to test

• spin up your local gitlab instance
• enable the feature flag e.g. "Feature.enable(:security_on_demand_scans_feature_flag)" | be rails c
• login
• go to the graphql explorer
• get a project path, come up with a profile name and get a url
• run a mutation like shown in [0]

---

• [0]

  mutation {
    dastSiteProfileCreate(input: {fullPath: "root/on-demand-scans", profileName: "hello, world!", targetUrl: "https://filib.io"}) {
      id
    }
  }

Related Issue(s)

#225404 (closed)

Does this MR meet the acceptance criteria?

Conformity

• Changelog entry behind feature flag
• Documentation (if required)
• Code review guidelines
• Merge request performance guidelines
• Style guides
• Database guides
• Separation of EE specific content

Availability and Testing

• Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process.
• Tested in all supported browsers
• Informed Infrastructure department of a default or new setting change, if applicable per definition of done

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

• 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