Chore: Removed v0 flutter fragments (#7349)

* chore: remove v0 flutter fragment

* chore: remove move flutter fragment

* chore: remove the move page from the directory and remove move from pages completely

src/directory/directory.mjs

@@ -1737,9 +1737,6 @@ export const directory = {
                     {
                       path: 'src/pages/gen1/[platform]/build-ui/formbuilder/lifecycle/index.mdx'
                     },
-                    {
-                      path: 'src/pages/[platform]/prev/build-a-backend/storage/move/index.mdx'
-                    },
                     {
                       path: 'src/pages/gen1/[platform]/build-ui/formbuilder/call-to-action/index.mdx'
                     },

src/fragments/lib-v1/graphqlapi/native_common/authz/common.mdx

@@ -275,10 +275,6 @@ You can now configure a single GraphQL API to deliver private and public data. P
 
 As discussed in the above linked documentation, certain fields may be protected by different authorization types. This can lead the same query, mutation, or subscription to have different responses based on the authorization sent with the request; Therefore, it is recommended to use the different `friendly_name_<AuthMode>` as the `apiName` parameter in the `Amplify.API` call to reference each authorization type.
 
-import flutter18 from '/src/fragments/lib-v1/graphqlapi/flutter/authz/auth_mode.mdx';
-
-<Fragments fragments={{ flutter: flutter18 }} />
-
 The following snippets highlight the new values in the `amplifyconfiguration.json`/`.dart` and the client code configurations.
 
 The `friendly_name` illustrated here is created from Amplify CLI prompt. There are 4 clients in this configuration that connect to the same API except that they use different `AuthMode`.