Medical Diagnoser (#601)

## Pull Request for PyVerse 💡

### Requesting to submit a pull request to the PyVerse repository.

---

#### Issue Title
**Please enter the title of the issue related to your pull request.**  
Medical Diagnoser

- [X] I have provided the issue title.

---

#### Info about the Related Issue
**What's the goal of the project?** To implement a Medical Diagnosis and
Prescription System using Deep Learning techniques.


- [X} I have described the aim of the project.

---

#### Name
**Please mention your name.**  
Venkata Ramana Billana
- [X] I have provided my name.

---

#### GitHub ID
**Please mention your GitHub ID.**  
ramana2074
- [X] I have provided my GitHub ID.

---

#### Email ID
**Please mention your email ID for further communication.**  
*Enter your email ID here.*
[email protected]

- [X] I have provided my email ID.

---

#### Identify Yourself
**Mention in which program you are contributing (e.g., WoB, GSSOC, SSOC,
SWOC).**
*Enter your participant role here.*
GSSOC Extended Contributor 2024
- [X] I have mentioned my participant role.

---

#### Closes
**Enter the issue number that will be closed through this PR.**  
*Closes: #issue-number*
#565 
- [X] I have provided the issue number.

---

#### Describe the Add-ons or Changes You've Made
**Give a clear description of what you have added or modified.**  
This project implements a Medical Diagnosis and Prescription System
using Deep Learning techniques. By utilizing the power of Long
Short-Term Memory (LSTM) networks, this system is capable of analyzing a
patient's symptoms and providing an accurate diagnosis along with the
recommended medication. The LSTM model, a variant of Recurrent Neural
Networks (RNN), is particularly suited for processing sequential data
like patient symptoms and offers significant advantages when dealing
with textual data.
- [X] I have described my changes.

---

#### Type of Change
**Select the type of change:**  
- [ ] Bug fix (non-breaking change which fixes an issue)
- [X] New feature (non-breaking change which adds functionality)
- [ ] Code style update (formatting, local variables)
- [ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected)
- [ ] This change requires a documentation update

---

#### How Has This Been Tested?
**Describe how your changes have been tested.**I
It has been test against different prescriptions and symptoms
- [X] I have described my testing process.

---

#### Checklist
**Please confirm the following:**  
- [X] My code follows the guidelines of this project.
- [X] I have performed a self-review of my own code.
- [X] I have commented my code, particularly wherever it was hard to
understand.
- [X] I have made corresponding changes to the documentation.
- [X] My changes generate no new warnings.
- [X] I have added things that prove my fix is effective or that my
feature works.
- [X] Any dependent changes have been merged and published in downstream
modules.