Change bard urls to gemini in docs and core modules

[sudoAlireza]

Pull Request

Changes proposed in this pull request:

• Changed bard.google.com to gemini.google.com in core modules
• Change Bard urls to Gemini urls in Docs

Description:

Google rebranded Bard to Gemini, and the unofficial API is encountering errors.

Related Issues:

• Google renames its chatbot Bard to Gemini #275

Testing:

After modifying bard.google.com to gemini.google.com, my previous codes are functioning correctly. for testing:
Install Package:

pip install git+https://github.com/sudoFathi/Bard-API.git@Bard-To-Gemini-Changes

And run you former codes with BardAPI

To-Do:

• Change Bard urls to Gemini urls in other programming languages

[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.

🔎 Detected hardcoded secret in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
-		Base64 Basic Authentication	c5eadf6	bardapi/constants.py	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.

---

<sup>🦉 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.

Our GitHub checks need improvements? Share your feedbacks!</sup>