Update dependencies and fix issues in version 0.1.8

[ehsan-fj]

This pull request refines how passwords are handled for EPP contact and domain operations, ensuring that passwords are only auto-generated when required and not unnecessarily included in updates. It also improves robustness when handling missing data and updates test coverage accordingly. Additionally, the PR updates some dependencies and fixes a template naming typo.

Password handling improvements:

• Passwords are now auto-generated only during Contact.create() and Domain.create() if not supplied, and are no longer generated or included by default in update operations or in the base command logic. This prevents sending unnecessary passwords and aligns behavior with EPP best practices. [1] [2] [3]
• The command template for contacts now conditionally includes the <contact:authInfo> block only if a password is provided, preventing empty password fields in generated XML.

Robustness and bug fixes:

• The _data_to_dict method in Contact now safely handles cases where postal_info is None, preventing AttributeError and ensuring correct dictionary output.
• The Contact.update() method checks for the existence of postal_info before accessing its attributes, preventing errors during updates when this data is missing.

Template and import corrections:

• Fixed a typo in the contact creation XML template variable name (CONTACT_CREAT_XML → CONTACT_CREATE_XML) and updated all usages accordingly. [1] [2] [3]
• Removed an unused import of helper from base_command.py, and added it where needed. [1] [2] [3]

Test coverage enhancements:

• Added and updated tests to verify that passwords are only generated for create operations, not for updates, and that missing postal_info is handled gracefully. [1] [2] [3] [4]

Dependency updates:

• Updated several development dependencies to their latest versions for improved security and compatibility.