Fix incorrectly placed feature in CHANGELOG

Move incorrectly placed feature for PostgREST errors from v9.0.0 to Upcoming

CHANGELOG.md

@@ -22,6 +22,9 @@ This project adheres to [Semantic Versioning](http://semver.org/).
    + Uses the table primary key, so it needs a select privilege on the primary key columns
    + If no primary key is available, it will fallback to using the "ctid" system column(will also require a select privilege on it)
    + Doesn't work on views and it will throw an error if tried
+ - #1917, Add error codes with the `"PGRST"` prefix to the error response body to differentiate PostgREST errors from PostgreSQL errors - @laurenceisla
+ - #1917, Normalize the error response body by always having the `detail` and `hint` error fields with a `null` value if they are empty - @laurenceisla
+ - #2176, Errors raised with `SQLSTATE` now include the message and the code in the response body - @laurenceisla
 
 ### Fixed
 
@@ -71,9 +74,6 @@ This project adheres to [Semantic Versioning](http://semver.org/).
    + PostgreSQL versions below 14 can opt in to the new JSON GUCs by setting the `db-use-legacy-gucs` config option to false (true by default)
  - #1988, Allow specifying `unknown` for the `is` operator - @steve-chavez
  - #2031, Improve error message for ambiguous embedding and add a relevant hint that includes unambiguous embedding suggestions - @laurenceisla
- - #1917, Add error codes with the `"PGRST"` prefix to the error response body to differentiate PostgREST errors from PostgreSQL errors - @laurenceisla
- - #1917, Normalize the error response body by always having the `detail` and `hint` error fields with a `null` value if they are empty - @laurenceisla
- - #2176, Errors raised with `SQLSTATE` now include the message and the code in the response body - @laurenceisla
 
 ### Fixed