Reset pasword button working using JavaScript

[pinakviramgama]

🛠️ Fixes Issue

Fixes: #2832

👨‍💻 Description

What does this PR do?

The reset password button was not working prevoiusly

BEFORE :

NOW :

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
fin-veda	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Nov 6, 2024 1:28pm

[github-actions]

Thank you for submitting your chaotic pull request! 🙌 We'll review it as soon as possible. In the meantime, please ensure that your changes align with our chaotic CONTRIBUTING.md. If there are any specific instructions or feedback regarding your PR, we'll provide them here. Thanks again for your contribution! 😊

[netlify]

✅ Deploy Preview for getfinveda ready!

Name	Link
🔨 Latest commit	8b29720
🔍 Latest deploy log	https://app.netlify.com/sites/getfinveda/deploys/672b6eff5b563d0008b131c7
😎 Deploy Preview	https://deploy-preview-2872--getfinveda.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 34 Accessibility: 73 Best Practices: 75 SEO: 73 PWA: - View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[gitguardian]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
-	-	Generic High Entropy Secret	d3bdc90	node_modules/debug/.coveralls.yml	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secret safely. Learn here the best practices.
3. Revoke and rotate this secret.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}

[pinakviramgama]

Dear @Sampadatiwari , please merge this pull request

[pinakviramgama]

Dear @deepeshmlgupta , please merge this pull request

[deepeshmlgupta]

@ayush-that do review this PR