Updated to latest version of Flutter and Major bug fixes

[abhinavsinghring]

This code has so much unnecessary links between pages which doesn't make sense and makes hard to understand but anyway I did some changes to make it working at some extent.

• Added App Icon
• Changed App Name
• Added Native Splash Screen (Will work on every device)
• Route Changes
• Login and Sign Up with email now working
• Changed Pregnancy Details form fill up UI
• Added Profile Photo link to user's database
• Some UI components will be visible only when logged in and with details filled
• Some null safety bugs fixed

And there are so many changes so you should look by yourself if can be merged.

Thanks! 😊

[gitguardian]

⚠️ GitGuardian has uncovered 8 secrets 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 secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
6515564	Triggered	Google API Key	7d7f2b2	lib/utils/asset_helper.dart	View secret
6515564	Triggered	Google API Key	75d4e61	lib/utils/asset_helper.dart	View secret
6515564	Triggered	Google API Key	25f0ef5	lib/utils/asset_helper.dart	View secret
6515564	Triggered	Google API Key	75d4e61	lib/utils/asset_helper.dart	View secret
6515564	Triggered	Google API Key	43a7a4c	lib/utils/asset_helper.dart	View secret
6515564	Triggered	Google API Key	25f0ef5	lib/utils/asset_helper.dart	View secret
6515564	Triggered	Google API Key	7d7f2b2	lib/utils/asset_helper.dart	View secret
6515564	Triggered	Google API Key	43a7a4c	lib/utils/asset_helper.dart	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 secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
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.}