Another usage of limit param

[dataders]

Description

This is a follow-on to #392 to completely implement the changes needed as a result of dbt-labs/dbt-core#7545

Previously, I had only given guidance that DatabricksConnectionManager.execute() was the only place where limit should be added.

However, TIL that dbt-databricks overrides dbt-core's BaseAdapter.execute(), therefore that function signature must also be updated. This was a miss on my part, because AFAIK, dbt-databricks is the only adapter doing this. I updated dbt-labs/dbt-core#7958 to reflect this information.

Perhaps there's a follow-up item where can revisit the use case of overriding that method and if there's an alternative way to handle __tmp tables.

Checklist

• I have run this code in development and it appears to resolve the stated issue
• This PR includes tests, or tests are not required/relevant for this PR
• I have updated the CHANGELOG.md and added information about my change to the "dbt-databricks next" section.