Add global_id field to DastScannerProfiles

What does this MR do?

adds global_id field to dast_scanner_profile create mutation and query type. the other graphql mutations/queries use the enriched type, rather than GraphQL::ID, which will be an issue for api consumers (e.g. frontend). since this mutation has been released, i've opted to add a new field rather than change the type of the old one and marked the old one as deprecated.

it's not ideal but it looks like there's a move towards using the new, finer grained, scalar types across the board.

Related Issue(s)

#238963 (closed)

Does this MR meet the acceptance criteria?

Conformity

• Changelog entry
• 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