FIX: Update and publish benchmark script (#152)

### Work Item / Issue Reference  
<!-- 
IMPORTANT: Please follow the PR template guidelines below.
For mssql-python maintainers: Insert your ADO Work Item ID below (e.g.
AB#37452)
For external contributors: Insert Github Issue number below (e.g. #149)
Only one reference is required - either GitHub issue OR ADO Work Item.
-->

<!-- mssql-python maintainers: ADO Work Item -->
>
[AB#38033](https://sqlclientdrivers.visualstudio.com/c6d89619-62de-46a0-8b46-70b92a84d85e/_workitems/edit/38033)

<!-- External contributors: GitHub Issue -->
> GitHub Issue: #<ISSUE_NUMBER>

-------------------------------------------------------------------
### Summary   
<!-- Insert your summary of changes below. Minimum 10 characters
required. -->
This pull request introduces a new `benchmarks` directory with a
`README.md` file to guide users on how to run database performance
benchmarks using `pyodbc` and `mssql_python`. The documentation provides
detailed instructions and highlights the key features of the benchmark
script.

### Documentation for Benchmarking:

*
[`benchmarks/README.md`](diffhunk://#diff-576c27794bae284efc278336a16d0649aaf599973a64d4b65dc67bc99bb7f000R1-R40):
Added a comprehensive guide explaining the purpose of benchmarks, setup
instructions, and how to run them using `richbench`. The guide also
outlines key features of the `bench_mssql.py` script, such as support
for various database operations, error handling, and automated
setup/cleanup.

<!-- 
### PR Title Guide

> For feature requests
FEAT: (short-description)

> For non-feature requests like test case updates, config updates ,
dependency updates etc
CHORE: (short-description) 

> For Fix requests
FIX: (short-description)

> For doc update requests 
DOC: (short-description)

> For Formatting, indentation, or styling update
STYLE: (short-description)

> For Refactor, without any feature changes
REFACTOR: (short-description)

> For release related changes, without any feature changes
RELEASE: #<RELEASE_VERSION> (short-description) 

### Contribution Guidelines

External contributors:
- Create a GitHub issue first:
https://github.com/microsoft/mssql-python/issues/new
- Link the GitHub issue in the "GitHub Issue" section above
- Follow the PR title format and provide a meaningful summary

mssql-python maintainers:
- Create an ADO Work Item following internal processes
- Link the ADO Work Item in the "ADO Work Item" section above  
- Follow the PR title format and provide a meaningful summary
-->

---------

Co-authored-by: Gaurav Sharma <sharmag@microsoft.com>

Author: gargsaumya

benchmarks/README.md

@@ -0,0 +1,40 @@
+# Benchmarks
+
+This directory contains benchmark scripts for testing the performance of various database operations using `pyodbc` and `mssql_python`. The goal is to evaluate and compare the performance of these libraries for common database operations.
+
+## Why Benchmarks?
+- To measure the efficiency of `pyodbc` and `mssql_python` in handling database operations.
+- To identify performance bottlenecks and optimize database interactions.
+- To ensure the reliability and scalability of the libraries under different workloads.
+
+## How to Run Benchmarks
+1. **Set Up the Environment Variable**:
+   - Ensure you have a running SQL Server instance.
+   - Set the `DB_CONNECTION_STRING` environment variable with the connection string to your database. For example:
+     ```cmd
+     set DB_CONNECTION_STRING=Server=your_server;Database=your_database;UID=your_user;PWD=your_password;
+     ```
+
+2. **Install Richbench - Benchmarking Tool**:
+   - Install richbench :
+     ```cmd
+     pip install richbench
+     ```
+
+3. **Run the Benchmarks**:
+   - Execute richbench from the parent folder (mssql-python) :
+     ```cmd
+     richbench benchmarks
+     ```
+     Results will be displayed in the terminal with detailed performance metrics.
+
+## Key Features of `bench_mssql.py`
+- **Comprehensive Benchmarks**: Includes SELECT, INSERT, UPDATE, DELETE, complex queries, stored procedures, and transaction handling.
+- **Error Handling**: Each benchmark function is wrapped with error handling to ensure smooth execution.
+- **Progress Messages**: Clear progress messages are printed during execution for better visibility.
+- **Automated Setup and Cleanup**: The script automatically sets up and cleans up the database environment before and after the benchmarks.
+
+## Notes
+- Ensure the database user has the necessary permissions to create and drop tables and stored procedures.
+- The script uses permanent tables prefixed with `perfbenchmark_` for benchmarking purposes.
+- A stored procedure named `perfbenchmark_stored_procedure` is created and used during the benchmarks.