Added env parser inside the library

[coderx31]

Guidelines

1. Please complete the below template before submitting the PR. PR will be rejected if this is not completed.
2. Please tag issue number to title. Example: [01] New Feature X
3. Please do not modify the template.

Description

Please include a summary of the changes and the related issue.

List any dependencies that are required for this change.

Introduced new function to wrap the env.Parse function. Therefore "github.com/caarlos0/env/v11"
no longer will be a direct dependency for users

Issue

Please provide the relevant issue link.
#17

Type of change

Please mark [ x ] which are relevant.

• [ ] Bug fix (non-breaking change which fixes the issue)
• [ x ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality)
• [ ] This change requires a documentation update

Checklist

• [ x ] I have added the issue number and link to this PR.
• [ x ] My PR is only for one issue. If not please mention all the issues above.
• [ x ] My code follows the style guidelines of this project
• [ x ] I have performed a self-review of my 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 generates no new warnings
• [ x ] I have added tests that prove my fix is effective or my feature works
• [ x ] New and existing unit tests pass locally with my changes

Test Summary / Screenshots

Please provide the test summary and necessary screenshots
locally testing results

unit tests results

[wgarunap]

nice work! needs small improvements on the tests.

[wgarunap]

suggest to have a PR name like Added env parser inside the library, no need to mention the issue id as we already linked the PR with the issue. @coderx31