support aliases

[egan8888]

Adds support for aliases when generating the query.

Previously column names would be generated as {dataSourceName}__{columnName}. Now, if alias field is provided in schema, that will be used instead. If alias is not provided, we fall back on the original format.

Query generation with resolution is also updated to make use of aliases.

• For unresolved columns, column names used to be of the form __base_query__{dataSourceName}__{columnName}. Now the column name will be the alias if provided else {dataSourceName}__{columnName}

• For resolved columns, column names used to be of the form {dataSourceName}__{columnName}__{resolvedColumnName. Now it will be of the form {columnNameAlias} - {resolvedColumnNameAlias} if the relevant aliases are provided, else {dataSourceName}__{columnName} - {resolvedColumnName}.

Included tests for all changes.

This PR also includes some formatting changes from the auto-formatter.

https://app.devrev.ai/devrev/works/ISS-191518

[zaidjan-devrev]

Can we try avoiding the alias Record<string, string> prop everywhere. Would it be possible to populate the alias from the tableSchema or other metadata that is present in these functions. If the metadata is not introduced, can we add a prop for that?