chore: add cookie storage example (#6554)

Author: israx

src/pages/[platform]/build-a-backend/auth/manage-user-session/index.mdx

@@ -156,7 +156,7 @@ In Amplify the `localStorage` is the default storage mechanism. It saves the tok
 <Block name="TypeScript">
 
 ```ts
-import { Amplify, ResourcesConfig } from 'aws-amplify';
+import { Amplify, type ResourcesConfig } from 'aws-amplify';
 import { defaultStorage } from 'aws-amplify/utils';
 import { cognitoUserPoolsTokenProvider } from 'aws-amplify/auth/cognito';
 
@@ -199,6 +199,57 @@ cognitoUserPoolsTokenProvider.setKeyValueStorage(defaultStorage);
 </Block>
 </BlockSwitcher>
 
+#### Cookie Storage
+
+`CookieStorage` saves the tokens in the browser's `Cookies`. The cookies will persist across browser sessions and tabs. You can explicitly set to this storage by calling:
+
+<BlockSwitcher>
+<Block name="TypeScript">
+
+```ts
+import { Amplify, type ResourcesConfig } from 'aws-amplify';
+import { CookieStorage } from 'aws-amplify/utils';
+import { cognitoUserPoolsTokenProvider } from 'aws-amplify/auth/cognito';
+
+const authConfig: ResourcesConfig['Auth'] = {
+  Cognito: {
+    userPoolId: 'your_user_pool_id',
+    userPoolClientId: 'your_user_pool_client_id'
+  }
+};
+
+Amplify.configure({
+  Auth: authConfig
+});
+
+cognitoUserPoolsTokenProvider.setKeyValueStorage(new CookieStorage());
+```
+
+</Block>
+<Block name="JavaScript">
+
+```javascript
+import { Amplify } from 'aws-amplify';
+import { CookieStorage } from 'aws-amplify/utils';
+import { cognitoUserPoolsTokenProvider } from 'aws-amplify/auth/cognito';
+
+const authConfig = {
+  Cognito: {
+    userPoolId: 'your_user_pool_id',
+    userPoolClientId: 'your_user_pool_client_id'
+  }
+};
+
+Amplify.configure({
+  Auth: authConfig
+});
+
+cognitoUserPoolsTokenProvider.setKeyValueStorage(new CookieStorage());
+```
+
+</Block>
+</BlockSwitcher>
+
 #### Browser Session Storage
 
 `sessionStorage` saves the tokens in the browser's `sessionStorage` and these tokens will clear when a tab is closed. The benefit to this storage mechanism is that the session only lasts as long as the browser is open and you can sign out users when they close the tab. You can update to this storage by calling:
@@ -207,7 +258,7 @@ cognitoUserPoolsTokenProvider.setKeyValueStorage(defaultStorage);
 <Block name="TypeScript">
 
 ```ts
-import { Amplify, ResourcesConfig } from 'aws-amplify';
+import { Amplify, type ResourcesConfig } from 'aws-amplify';
 import { sessionStorage } from 'aws-amplify/utils';
 import { cognitoUserPoolsTokenProvider } from 'aws-amplify/auth/cognito';
 
@@ -218,12 +269,9 @@ const authConfig: ResourcesConfig['Auth'] = {
   }
 };
 
-Amplify.configure(
-  {
-    Auth: authConfig
-  },
-  { Auth: { tokenProvider: cognitoUserPoolsTokenProvider } }
-);
+Amplify.configure({
+  Auth: authConfig
+});
 
 cognitoUserPoolsTokenProvider.setKeyValueStorage(sessionStorage);
 ```
@@ -261,7 +309,7 @@ You can implement your own custom storage mechanism by creating a class that imp
 <Block name="TypeScript">
 
 ```ts
-import { Amplify, ResourcesConfig } from 'aws-amplify';
+import { Amplify, type ResourcesConfig } from 'aws-amplify';
 import { KeyValueStorageInterface } from 'aws-amplify/utils';
 import { cognitoUserPoolsTokenProvider } from 'aws-amplify/auth/cognito';
 
@@ -288,12 +336,9 @@ class MyCustomStorage implements KeyValueStorageInterface {
   }
 }
 
-Amplify.configure(
-  {
-    Auth: authConfig
-  },
-  { Auth: { tokenProvider: cognitoUserPoolsTokenProvider } }
-);
+Amplify.configure({
+  Auth: authConfig
+});
 
 cognitoUserPoolsTokenProvider.setKeyValueStorage(new MyCustomStorage());
 ```