reconciling cosmos db postgresql and azure db postgresql flex.

[journeyman-msft]

Description

There are multiple folders with different names, however the code is very similar between the two. The main difference is that a user will have to run python connect_postgresql_flex.py or connect_cosmos_postgresql.py to choose which resource to use for the correct flow.

The user is expected to define the environment variable COSMOS_DB_POSTGRESQL_CONN_STRING and POSTGRESQL_FLEX_CONN_STRING in the .env, which will then update the promptflow connection postgressql_connection.

The major e2e sample folder names are now:

• rag-cosmos-postgresql-pgvector
• rag-postgresql-flex-pgvector

There are bite sized tool usage samples also:

• cosmos-postgresql-pgvector
• postgresql-flex-pgvector

Type of change

Please remove options that are not relevant.

• [] New feature: not breaking, new functionality
• [] New feature: may cause existing code to not work as expected
• [] Bug fix
• [X] Needs documentation update

Test and checks

Please describe how you've tested your file

• [X] tested via a notebook
• [X] tested via a testflow
• [X] only made sure the code is written correctly Checks
• [X] commented code for complex areas
• [X] updated readme with the new changes
• [X] changes not generating errors with the main flows in rag-vectorsearchtype directories (e.g rag-cosmos-mongo)
• [X] I have tested my implementation
• [X] I have updated environment.yaml file with any additional dependancies