Under current capabilities (as of 2023-12-15), it is not possible to edit spatial tables in a PostgreSQL database with native PostGIS geometry unless you first undertake the "Create Enterprise Geodatabase" process. (And that process requires an expensive enterprise license.)
This is true despite the fact that Esri expresses "support" for "using" native PostGIS geometry in this help section. It is true you can read such spatial tables (via query layer), and you can even load them in (via geoprocessing), but you cannot edit them. So that "support" is fairly limited when it comes to a core capability.
True, there are many cases when an "Enterprise Geodatabase" is advantageous. But there are other cases where it is not required and introduces unnecessary overhead. For very basic spatial data management, true support for PostgreSQL and PostGIS geometry would include editing from Pro.
