Read the name and properties of the instance only in getInstance service.

[xzyJavaX]

• If this pull request closes/resolves/fixes an existing issue, replace the issue number. Closes #10421
• Update the CHANGES log.

[wu-sheng]

If you want to add this, please make sure query dao would use this.

[wu-sheng]

@kezhenxu94 Please take a look.

[kezhenxu94]

Code level changes look good to me, but this may bring some troubles when future contributors use the getInstance and need the other fields like instance uuid, or id, they might have no idea why these two fields are null/empty

[wu-sheng]

Code level changes look good to me, but this may bring some troubles when future contributors use the getInstance and need the other fields like instance uuid, or id, they might have no idea why these two fields are null/empty

@xzyJavaX You are better to keep consistent logic in JDBCMetadataQueryDAO`

[wu-sheng]

I think it is wrong to build only two columns, even for BanyanDB.

@lujiajing1126 It seems BanyanDB implementation doesn't return required fields.

[wu-sheng]

Close for now until we have a real use case to use Sources of ElasticSearch accessing.