chore: Update README.md to reflect array order significance

[helmturner]

PR Checklist

• Addresses an existing open issue: fixes #000
• That issue was marked as status: accepting prs
• Steps in CONTRIBUTING.md were taken

Overview

Update docs to point out potential gotcha re: array order of custom serializers

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
tupleson-async	✅ Ready (Inspect)	Visit Preview	Oct 22, 2023 9:57am

[codecov]

Codecov Report

Merging #79 (5d8266c) into main (d969451) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #79   +/-   ##
=======================================
  Coverage   96.27%   96.27%           
=======================================
  Files          30       30           
  Lines        1827     1827           
  Branches      194      194           
=======================================
  Hits         1759     1759           
  Misses         66       66           
  Partials        2        2           

Flag	Coverage Δ
unit	96.27% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

[github-actions]

PR Compliance Checks

Thank you for your Pull Request! We have run several checks on this pull request in order to make sure it's suitable for merging into this project. The results are listed in the following section.

Issue Reference

In order to be considered for merging, the pull request description must refer to a specific issue number. This is described in our Contributing Guide. We are closing this pull request for now but you can update the pull request description and reopen the pull request.
The check is looking for a phrase similar to: "Fixes #XYZ" or "Resolves #XYZ" where XYZ is the issue number that this PR is meant to address.