GraphQL: Remove deprecated fields (%14.0)

Following https://docs.gitlab.com/ee/api/graphql/#deprecation-process, this issue is a chore to remove the fields that should be removed from the GraphQL API for %14.0.

See !44866 (merged) for a template 🙂

• Create MR to remove from code (see !44866 (merged)), and arrange it to be merged sometime in %13.11
• Create MR to add fields to 'removed items' section of the docs (see !45377 (merged))
• Ping @gweaver so the removed fields notice can be added into the release post
• Create an issue like this one for %14.6 and tag @gweaver. Ask him to set the milestone to %14.5 and the due date to the 16th of that month (some days before the release) - #334278 (closed)

Related to #239260 (closed)

Removals

Taken from the 14.0 breaking changes blog post announcement -- https://11247-blog-post-for-breaking-changes-coming-in-14-0.about.gitlab-review.app/blog/2021/05/10/announce-breaking-changes-14-0/:

Removal MR !63293 (merged)

• Mutations::Todos::MarkAllDone - updated_ids
• Mutations::Todos::RestoreMany - updated_ids
• Mutations::DastScannerProfiles::Create - global_id
• Types::SnippetType - blob
• Types::DastScannerProfileType - global_id
• EE::Types::GroupType - vulnerabilities_count_by_day_and_severity
• EE::Types::QueryType - vulnerabilities_count_by_day_and_severity
• DeprecatedMutations (concern**) - AddAwardEmoji
• DeprecatedMutations (concern**) - RemoveAwardEmoji
• DeprecatedMutations (concern**) - ToggleAwardEmoji
• EE::Types::DeprecatedMutations (concern***) - Mutations::Pipelines::RunDastScan
• EE::Types::DeprecatedMutations (concern***) - Mutations::Vulnerabilities::Dismiss
• EE::Types::DeprecatedMutations (concern***) - Mutations::Vulnerabilities::RevertToDetected

Removal MR !63511 (merged)

• TimeFrameArguments (concern*) - start_date
• TimeFrameArguments (concern*) - end_date

Removal MR !63470 (closed)

• Types::SortEnum - updated_desc
• Types::SortEnum - updated_asc
• Types::SortEnum - created_desc
• Types::SortEnum - created_asc