update cli-legacy relative links

Author: Jacob Logan

src/fragments/lib-v1/auth/native_common/delete_user/common.mdx

@@ -10,7 +10,7 @@ Depending on your application, data associated with your user may be stored in o
 
 <Callout warning>
 
-Before invoking the “delete user” API, you can first delete associated user data from the GraphQL API. For example, if you are using Amplify CLI's [GraphQL transformer](https://docs.amplify.aws/cli-legacy/graphql-transformer/overview/) to persist user data via [owner based access control](/[platform]/build-a-backend/graphqlapi/customize-auth//#per-user--owner-based-data-access), you could follow [these instructions](https://gist.github.com/aws-amplify-ops/27954c421bd72930874d48c15c284807) to delete associated user data.
+Before invoking the “delete user” API, you can first delete associated user data from the GraphQL API. For example, if you are using Amplify CLI's [GraphQL transformer](https://docs.amplify.aws/cli-legacy/overview/) to persist user data via [owner based access control](/[platform]/build-a-backend/graphqlapi/customize-auth//#per-user--owner-based-data-access), you could follow [these instructions](https://gist.github.com/aws-amplify-ops/27954c421bd72930874d48c15c284807) to delete associated user data.
 
 This allows you to address any guidelines that require your app to delete data associated with a user who deletes their account.
 

src/pages/[platform]/build-a-backend/graphqlapi/client-code-generation/index.mdx

@@ -30,7 +30,7 @@ export function getStaticProps(context) {
   };
 }
 
-<MigrationAlert url={'/[platform]/cli-legacy/graphql-transformer/codegen'} />
+<MigrationAlert url={'/[platform]/cli-legacy/codegen'} />
 
 "Codegen" generates native code for Swift (iOS), Java (Android), and JavaScript that represent your GraphQL API's data models. It can also generate GraphQL statements (queries, mutations, and subscriptions) so that you don't have to hand code them.
 

src/pages/[platform]/build-a-backend/graphqlapi/connect-machine-learning-services/index.mdx

@@ -30,9 +30,7 @@ export function getStaticProps(context) {
   };
 }
 
-<MigrationAlert
-  url={'/[platform]/cli-legacy/graphql-transformer/predictions'}
-/>
+<MigrationAlert url={'/[platform]/cli-legacy/predictions'} />
 
 Amplify allows you to identify text on an image, identify labels on an image, translate text, and synthesize speech from text with the `@predictions` directive.
 

src/pages/[platform]/build-a-backend/graphqlapi/custom-business-logic/index.mdx

@@ -31,9 +31,7 @@ export function getStaticProps(context) {
 }
 
 <MigrationAlert
-  url={
-    '/[platform]/[platform]/tools/cli-legacy/graphql-transformer/function-directive/'
-  }
+  url={'/[platform]/[platform]/tools/cli-legacy/function-directive/'}
 />
 
 Define your custom business logic in a Lambda function resolver, HTTP resolver, or VTL resolver and expose them in a GraphQL query or mutation. Extend or override Amplify-generated GraphQL resolvers to optimize for your specific use cases.

src/pages/[platform]/build-a-backend/graphqlapi/customize-authorization-rules/index.mdx

@@ -30,7 +30,7 @@ export function getStaticProps(context) {
   };
 }
 
-<MigrationAlert url={'/cli-legacy/graphql-transformer/auth'} />
+<MigrationAlert url={'/cli-legacy/auth'} />
 
 Use the `@auth` directive to configure authorization rules for public, sign-in user, per user, and per user group data access. **Authorization rules operate on the deny-by-default principle**. Meaning that if an authorization rule is not specifically configured, it is denied.
 

src/pages/[platform]/build-a-backend/graphqlapi/data-modeling/index.mdx

@@ -30,7 +30,7 @@ export function getStaticProps(context) {
   };
 }
 
-<MigrationAlert url={'/[platform]/cli-legacy/graphql-transformer/key'} />
+<MigrationAlert url={'/[platform]/cli-legacy/key'} />
 
 Amplify automatically creates Amazon DynamoDB database tables for GraphQL types annotated with the `@model` directive in your GraphQL schema. You can create relations between the data models via the `@hasOne`, `@hasMany`, `@belongsTo`, and `@manyToMany` directives.
 

src/pages/[platform]/build-a-backend/graphqlapi/search-and-result-aggregations/index.mdx

@@ -30,7 +30,7 @@ export function getStaticProps(context) {
   };
 }
 
-<MigrationAlert url={'/[platform]/cli-legacy/graphql-transformer/searchable'} />
+<MigrationAlert url={'/[platform]/cli-legacy/searchable'} />
 
 Add the `@searchable` directive to an `@model` type to enable OpenSearch-based data search and result aggregations. This gives you the ability to:
 

src/pages/[platform]/tools/cli/project/troubleshooting/index.mdx

@@ -46,7 +46,7 @@ To debug deployment issues, it's helpful to understand the [file structure of yo
 To debug deployment issues in projects with GraphQL API, it's helpful to understand the various artifacts generated by Amplify in a GraphQL project.
 
 1. GraphQL schema VTL generation: The Amplify CLI GraphQL workflow uses the [AWS AppSync service](https://docs.aws.amazon.com/appsync/latest/devguide/system-overview-and-architecture.html) to provision the GraphQL API. The `amplify api gql-compile` command transpiles the GraphQL schema provided by the developer and generates all the artifacts required to deploy the API in AWS.
-   - Directives like [@model](/[platform]/build-a-backend/graphqlapi/data-modeling//), [@function](/[platform]/tools/cli-legacy/graphql-transformer/function-directive//), [@auth](/cli/graphql/authorization-rules/), and [@searchable](/[platform]/build-a-backend/graphqlapi/search-and-result-aggregations/) in the GraphQL schema are used to generate CloudFormation and provision AWS resources.
+   - Directives like [@model](/[platform]/build-a-backend/graphqlapi/data-modeling//), [@function](/[platform]/tools/cli-legacy/function-directive//), [@auth](/cli/graphql/authorization-rules/), and [@searchable](/[platform]/build-a-backend/graphqlapi/search-and-result-aggregations/) in the GraphQL schema are used to generate CloudFormation and provision AWS resources.
    - The GraphQL resolvers for Query, Mutation or Subscription are converted into [VTL (Velocity Template Language)](https://docs.aws.amazon.com/appsync/latest/devguide/resolver-mapping-template-reference-programming-guide.html) files. AWS AppSync uses VTL to translate GraphQL requests from clients into a request to your data source.
 1. GraphQL schema client-side code generation: The Amplify CLI GraphQL workflow allows developers to generate client-side code for web and mobile clients using the `amplify codegen` command. Read the [Amplify code generation documentation](/[platform]/build-a-backend/graphqlapi/client-code-generation/) prior to debugging any client-side code generation issues.
 

src/pages/[platform]/tools/console/data/data-model/index.mdx

@@ -51,7 +51,7 @@ Skip ahead to [relationships](/[platform]/tools/console/data/relationships/) or
 
 ## Data modeling in Amplify Studio
 
-The Studio data model designer provides a visual way to define your app's data model, relationships, and authorization rules. Studio generates a `schema.graphql` GraphQL Transform for the data model you create, and adds this to your Amplify project. To learn more about how the GraphQl transform works, see [GraphQL Transform Overview](/[platform]/tools/cli-legacy/graphql-transformer/overview/).
+The Studio data model designer provides a visual way to define your app's data model, relationships, and authorization rules. Studio generates a `schema.graphql` GraphQL Transform for the data model you create, and adds this to your Amplify project. To learn more about how the GraphQl transform works, see [GraphQL Transform Overview](/[platform]/tools/cli-legacy/overview/).
 
 ![Screen recording of the process for adding a data model in data modelling page](/images/console/datamodel.gif)