Remove virtual interface in SchemaProviderIf

[critical27]

What type of PR is this?

• bug
• feature
• enhancement

What problem(s) does this PR solve?

Issue(s) number:

Description:

Follow up of #5381, since RowReader has been removed, we could remove the virtual interface SchemaProviderIf further more. It has two derived class, NebulaSchemaProvider is the one we used, ResultSchemaProvider is the one that compatible with RowReaderV1, which is not used anymore.

How do you solve it?

In this PR, all schema is replaced with NebulaSchemaProvider, the base SchemaProviderIf and derived ResultSchemaProvider along with outdated test, RowReaderV1 are removed.

Special notes for your reviewer, ex. impact of this fix, design document, etc:

Checklist:

Tests:

• Unit test(positive and negative cases)
• Function test
• Performance test
• N/A

Affects:

• Documentation affected (Please add the label if documentation needs to be modified.)
• Incompatibility (If it breaks the compatibility, please describe it and add the label.）
• If it's needed to cherry-pick (If cherry-pick to some branches is required, please label the destination version(s).)
• Performance impacted: Consumes more CPU/Memory

Release notes:

Please confirm whether to be reflected in release notes and how to describe:

ex. Fixed the bug .....

[pengweisong]

if index_ out of range, operator*() will raise exception. Is this expected?

[pengweisong]

Good job