Bardapi

- Fixed printing errors in the ChatBard class.
- Made some modifications to docstrings and others.

- Added missing docstrings due to the addition of new features.
- Implemented try-except with error suppression in code for additional functionalities like images.
- Made several improvements to existing features.

While striving for clean and efficient code, I currently have limited time due to frequent internal interface changes at Google and my personal projects. Therefore, my goal is to focus on maintaining the main functionality (returning results as text). Contributors can help by addressing the issues that are created.

If you would like to become the main maintainer of the Bard API, please open a discussion page.

- Some errors in ChatBard have been fixed. However, it is recommended not to pass the value of the token through input.

- Modify translation-related code to accommodate changes in the Google API interface. you can use the `language` argument.
- Additionally, official usage of Google Cloud Translation API is available. For commercial use and others, please make sure to use `google_translator_api_key` to access the official translation API.

Due to changes in the Google interface, a bug has been fixed in the temporary release of version 0.1.18. We are preparing for the release of version 0.1.19, which will include checks for the remaining features. Additionally, starting from version 0.1.18, the GitHub version of BardAPI will be synchronized with the PyPI version and released simultaneously.

- Add `conversation_id` as argument of Bard class <br><br>

1. [reusable-session-object](https://github.com/dsdanielpark/Bard-API#reusable-session-object)
When using the `reusable session` as an argument in the Bard class, Bard can remember your previous prompts.


2. [fix-conversation-id-fix-context](https://github.com/dsdanielpark/Bard-API/blob/main/README_DEV.md#fix-conversation-id-fix-context)
When using the `reusable session` and `conversation_id` as arguments in the Bard class, Bard not only remembers your previous prompts but can also provide consistent responses.
By examining the contents in the response, you can identify several answer candidates with unique conversation_ids. If you find a conversation_id that you prefer, you can pass it as an argument to receive consistent responses from that specific Bard.