feat: support custom driver version for local testing of olake changes

[vishalm0509]

Description

The goal of this PR is to bridge the gap between development on the olake core (CLI) and the olake-ui. It introduces a CUSTOM_DRIVER_VERSION configuration that allows developers to build local driver images and use them immediately in the UI without semantic versioning restrictions.

• Local Image Injection: The value of CUSTOM_DRIVER_VERSION is automatically appended to the versions list for all connectors, making it selectable from the UI.
• Semver Bypass: Compatibility gates are bypassed when a custom version is active.
• Workflow Refactoring: Centralized the check logic to ensure developers don't have to manually update version across the codebase when testing new CLI changes or spec/ui-schema changes.

Fixes # (issue)

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

• Scenario A
• Scenario B

Screenshots or Recordings

Related PR's (If Any):

datazip-inc/olake-docs#351

[deepanshupal09-datazip]

I was thinking about how we can simplify the configuration a bit more. Since we already use runmode = localdev for testing local UI changes, what if we use that existing runmode check instead of introducing APP_ENV?

We could also just specify CUSTOM_DRIVER_VERSION directly in app.conf. This way, developers wouldn't have to manage two separate environment modes, and all the local configuration stays in one central place.

What do you think about this approach?

[deepanshupal09-datazip]

LGTM