Updated to the GET /handlers Endpoint to Support Forms in the GUI

[MinuraPunchihewa]

Description

At the moment, through our GUI, it is not possible to initialize all of our integrations through the forms section. The reason for this is because certain information that is required for the form is maintained as constants here in the front-end repository.

It would be more robust and extensible if this information can be delivered through our API endpoints and the objective of this PR is to accomplish that. This is done by introducing the following new attributes to our existing GET /handlers endpoint,

• most_popular: determined by querying the top 10 data sources and AI engines as per our data warehouse in BigQuery.
• is_aws: determined checking certain keywords against the title of the integration.
• is_new: determined by checking the creation/modification date of the about.py file of each integration.

Is this a good way to go about it? The additional computation will require a little more time for this endpoint to return a response. Should this maybe be separated out to a new endpoint?

Type of change

• ⚡ New feature (non-breaking change which adds functionality)

Verification Process

To ensure the changes are working as expected:

• Test Location: Specify the URL or path for testing.
• Verification Steps: Outline the steps or queries needed to validate the change. Include any data, configurations, or actions required to reproduce or see the new functionality.

Checklist:

• My code follows the style guidelines(PEP 8) of MindsDB.
• I have appropriately commented on my code, especially in complex areas.
• Necessary documentation updates are either made or tracked in issues.
• Relevant unit and integration tests are updated or added.