Resolve Publishing to Maven Central and Documentation Deployment Issues

[teogor]

This pull request addresses the encountered errors while publishing the project to Maven Central and deploying the documentation. The specific issues tackled include:

1. Missing License in POM: The project's POM file lacked a license declaration, which is mandatory for Maven Central publication. A valid license declaration has been added to comply with Maven Central's guidelines.

2. Incomplete POM License Declaration: The initial license declaration in the POM file was incomplete, missing the license URL. The license declaration has been updated to include the complete license name and URL.

3. Erroneous Documentation Deployment Path: The documentation deployment process was using an incorrect path, leading to deployment failures. The deployment path has been corrected to ensure proper documentation placement.

4. Missing Gradle Properties for Maven Central Credentials: The Gradle properties file lacked the required credentials (mavenCentralUsername and mavenCentralPassword) for accessing Maven Central. These credentials have been added to the properties file to enable artifact publication.

5. Unused pom Closure: The pom closure within the mavenPublishing block was not being invoked for the Android library, preventing POM configuration. The mavenPublishing block has been updated to use the android-maven-publish plugin instead, which properly handles POM configuration for Android libraries.