[native] Add support for optional velox.properties file

[majetideepak]

Description

Velox config has no required fields and therefore velox.properties should be optional.
From a Presto user perspective, existing config files (config.properties, node.properties)
for Java should work for Prestissimo as well.

Motivation and Context

Make Prestissimo config aligned to Presto Java

Impact

velox.properties is now optional.

Test Plan

Tested locally.

Contributor checklist

• Please make sure your submission complies with our development, formatting, commit message, and attribution guidelines.
• 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.

== NO RELEASE NOTE ==

[amitkdutta]

Looks good. Thanks @majetideepak

We had a discussion in #20406
My personal opinion is we stick with config properties and remove velox properties file - one less config to manage and eases deployment.

[majetideepak]

remove velox properties file

@amitkdutta Let's bring this up in the next Prestissimo WG meeting. CC: @aditi-pandit

[amitkdutta]

remove velox properties file

@amitkdutta Let's bring this up in the next Prestissimo WG meeting. CC: @aditi-pandit

CC: @spershin