[native] Fix MV mapping

[zation99]

Description

The original approach will cause a "Unsupported table writer handle" error. We should use InsertHandle with the MaterializedViewHandle key.
The order also needs to have MaterializedViewHandle key before InsertHandle key, otherwise the insertHandle type will be replaced with MaterializedViewHandle.

Motivation and Context

Impact

Test Plan

refresh materialized view query

Contributor checklist

• Please make sure your submission complies with our contributing guide, in particular code style and commit standards.
• PR description addresses the issue accurately and concisely. If the change is non-trivial, a GitHub Issue is referenced.
• Documented new properties (with its default value), SQL syntax, functions, or other functionality.
• If release notes are required, they follow the release notes guidelines.
• Adequate tests were added if applicable.
• CI passed.

Release Notes

Please follow release notes guidelines and fill in the release notes below.

== NO RELEASE NOTE ==

[aditi-pandit]

@zation99 : Is this the only change required for RefreshMaterializedView ? Does MaterializedViewHandle map to InsertTableHandle and then the rest of Velox code work as is for Materialized Views ? If yes, then would be great if you add an e2e test in https://github.com/prestodb/presto/blob/master/presto-native-execution/src/test/java/com/facebook/presto/nativeworker as well.

[gggrace14]

Prestissimo. Nice!

[zation99]

@zation99 : Is this the only change required for RefreshMaterializedView ? Does MaterializedViewHandle map to InsertTableHandle and then the rest of Velox code work as is for Materialized Views ? If yes, then would be great if you add an e2e test in https://github.com/prestodb/presto/blob/master/presto-native-execution/src/test/java/com/facebook/presto/nativeworker as well.

Oh sorry I missed your comment. Yes that's all needed and Velox uses InsertHandle for this.
Let me add an e2e test in a follow-up PR.