feat: update README.md to trigger release (supabase#1425)

## What kind of change does this PR introduce?

It seems like in v2.141.0 `release-please` succeeded but there was a
[likely
transient](https://github.com/supabase/gotrue/actions/runs/7889273761/job/21528885508#step:7:30)
failure in the build.

It seems like release-please needs to run before an image can be
published. However, since release please has completed for v2.141.0 it's
not possible to publish an image again since `release-please` re-runs of
v2.141.0 will lead to early termination since v2.141.0 has already been
published.

We publish a new version to get around this. These are some README
changes to trigger the publication of a new version

Co-authored-by: joel <joel@joels-MacBook-Pro.local>

README.md

@@ -143,13 +143,9 @@ comprehensive list of those features:
    configuration parameter.
 2. System user (zero UUID user).
 3. Super admin via the `is_super_admin` column.
-4. SAML sign-in provider via the `GOTRUE_SAML_ENABLED` configuration
-   parameter. (A different implementation for SAML may appear in the future
-   which will be supported.)
-5. Support for MySQL based databases. (Only Postgres is supported.)
-6. Group information in JWTs via `GOTRUE_JWT_ADMIN_GROUP_NAME` and other
+4. Group information in JWTs via `GOTRUE_JWT_ADMIN_GROUP_NAME` and other
    configuration fields.
-7. Symmetrics JWTs. In the future it is very likely that Auth will begin
+5. Symmetrics JWTs. In the future it is very likely that Auth will begin
    issuing asymmetric JWTs (subject to configuration), so do not rely on the
    assumption that only HS256 signed JWTs will be issued long term.