Add issue templates

[vanshambansal]

Description

This pull request introduces four new issue templates to improve the categorization and management of issues within the repository:

1. Re-Implementation Template:
   A template for proposing the re-implementation of existing features or code with the aim of improving performance, readability, or efficiency, while maintaining the original functionality.

2. Refactor To Enhance Template:
   A template for suggesting code refactoring that improves maintainability, structure, or adheres to best practices, without changing the core functionality.

3. Configuration Change Template:
   A template for issues related to changes in the project’s configuration, such as adjustments to build tools, CI/CD pipelines, or environment-specific settings.

4. Security Improvement Template:
   A template for identifying potential security risks and suggesting improvements to harden the codebase against vulnerabilities.

These templates are part of the effort to add more detailed issue types, enhancing the issue reporting process and improving overall project organization.

Fixes #356 (Add More Issue Types)

Type of change

Please delete options that are not relevant.

• [ ] Bug fix (non-breaking change which fixes an issue)
• [x] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [ ] Refactor (does not change functionality, e.g. code style improvements, linting)
• [ ] Documentation update

How Has This Been Tested?

This change doesn't require testing as it only adds new templates to the repository. To verify, ensure that the templates appear correctly when creating an issue. No functionality has been changed.

Checklist:

• [x] My code follows the style guidelines of this project
• [x] I have performed a self-review of my own code
• [x] I have commented my code, particularly in hard-to-understand areas
• [x] I have made corresponding changes to the documentation
• [x] My changes generate no new warnings
• [ ] I have added tests that prove my fix is effective or that my feature works
• [ ] New and existing unit tests pass locally with my changes
• [ ] Any dependent changes have been merged and published in downstream modules
• [x] I have checked my code and corrected any misspellings

Maintainer Checklist

• [ ] closes #356 (Add More Issue Types)
• [ ] Tag the PR with the appropriate labels

[Aarush-Acharya]

Configuration Change Description: Involves changes to the project's configuration, such as build tools, CI/CD pipeline adjustments, or environment-specific settings.

Security Improvement Description: Focuses on identifying potential security risks and requesting improvements to harden the codebase against vulnerabilities.

Please add these two as well @vanshambansal

[vanshambansal]

Configuration Change Description: Involves changes to the project's configuration, such as build tools, CI/CD pipeline adjustments, or environment-specific settings.

Security Improvement Description: Focuses on identifying potential security risks and requesting improvements to harden the codebase against vulnerabilities.

Please add these two as well @vanshambansal

Done!! Let me know if you need any further changes or if I can assist with anything else!

[Aarush-Acharya]

Hey @vanshambansal, good work

[vanshambansal]

Hey @vanshambansal, good work

thank u sir