Updates to JCOBridge 2.6.4-rcX introducing many breaking changes

[masesdevelopers]

Description

This PR introduces the usage of JCOBridge 2.6.4 which

• fix Class java.nio.ByteOrder was not found #717
• fix Usage of ByteBuffer breaks the application with Oracle 17 #722
• updates JNetReflector because latest JCOBridge introduced breaking changes:
  • Exception needs 3 constructor
  • ClazzOf overload can report exception without raise it, the template is able to use it accessing the class type
  • Every class inherited from JVMBridgeBase and JVMBridgeBase<T> needs:
    • a default constructor
    • a specific constructor like

public class CLASSNAME : JVMBridgeBase<CLASSNAME>
{
    public CLASSNAME() { }
    public CLASSNAME(IJVMBridgeBaseInitializer initializer) : base(initializer) { }
}

• developed classes are aligned to expected prototype of JCOBridge
• Updates Dispose pattern due to changes in JVMBridgeBase
• Managed last added properties of SetupJVMWrapper

Related Issue

fix #38

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.