Python-ms-core

New Features and Enhancements
- **Message Lock Renewal:** Implemented a mechanism to automatically renew message locks during processing. This ensures that messages remain active and are not returned to the queue for reprocessing while they are being handled.
- **Concurrent Message Processing:** Enhanced the system to process messages concurrently using a number of worker threads equal to the number of available CPU cores by default. Users can override this default by specifying the `max_concurrent_messages` parameter, for example, `core.get_topic(topic_name=topic_name, max_concurrent_messages=10)`. This optimization leverages system resources for improved performance and throughput.
- **Completion Acknowledgement:** Updated the processing flow to wait until message processing is fully completed before sending the acknowledgement of message completion. This change ensures reliable processing and accurate message handling.
- **Version Tracking:** Introduced a `version.py` file to maintain and track the package version. This addition facilitates version control and package management.
- **Unit Test Updates:** Updated unit test cases to cover the new features and enhancements, ensuring robust testing and quality assurance.
- **Documentation Update:** Updated the README file to reflect the new features and enhancements, providing clearer guidance and information for users.

- Adds extra checks in service bus for retries
- Additional logging done if there is no network and service bus crashes
- Service bus subscription picks up messages even if there is network outtage

- Added Unit Test Cases
- Updated Readme file

- Removed extra logs

This fixes the inconsistent listening behavior for the subscription of a topic from core.
- Due to the usage of `for message in receiver` logic in the topic, it is unknown when the loop will end and the core will stop listening to the topic.
- This is tried with various combinations and figured out that at probably 4 hours from launch, this happens. The root cause for this is the socket / connection timeout of the underlying amqp client which throws an exception when trying to iterate next message

Fix made:
- The above for loop is kept in an infinite while loop which triggers the creation of the receiver and subsequent listening to the messages.
- This was tested overnight with messages varying in the time differences (1h to 3h)
- Specific method to look for the fix `start_listening`

Reference task:
[302](https://dev.azure.com/TDEI-UW/TDEI/_workitems/edit/302)

- Fixed https://dev.azure.com/TDEI-UW/TDEI/_workitems/edit/302