Update the GitHub Markdown syntax for alerts in the readme.

See:

- https://github.com/orgs/community/discussions/16925
- https://github.blog/changelog/2023-12-14-new-markdown-extension-alerts-provide-distinctive-styling-for-significant-content/
- https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#alerts

Note this Prettier issue:

prettier/prettier#16454

changelog.md

@@ -48,6 +48,7 @@
 - Avoid using `return` in the middleware.
 - Added a new dev dependency [`async-listen`](https://npm.im/async-listen) to replace the test utility function `listen`.
 - Enabled the TypeScript compiler options `noUnusedLocals` and `noUnusedParameters` and used the prefix `_` for purposefully unused function parameters in tests.
+- Updated the GitHub Markdown syntax for alerts in the readme.
 
 ## 16.0.2
 

readme.md

@@ -8,7 +8,7 @@ Middleware and an [`Upload`](./GraphQLUpload.mjs) scalar to add support for [Gra
 
 ## Installation
 
-> **Note**
+> [!TIP]
 >
 > First, check if there are [GraphQL multipart request spec server implementations](https://github.com/jaydenseric/graphql-multipart-request-spec#server) (most for Node.js integrate [`graphql-upload`](https://npm.im/graphql-upload)) that are more suitable for your environment than a manual setup.