add case for information_schema.referenctial_constraints(1.1-dev)

[Ariznawlll]

What type of PR is this?

• API-change
• BUG
• Improvement
• Documentation
• Feature
• Test and CI
• Code Refactoring

Which issue(s) this PR fixes:

issue #https://github.com/matrixorigin/MO-Cloud/issues/2640

What this PR does / why we need it:

Add case for information_schema.referenctial_constraints

[matrix-meow]

@Ariznawlll Thanks for your contributions!

Pull Request Review:

Title:

The title of the pull request is clear and indicates the purpose of the changes made.

Body:

The body of the pull request provides relevant information about the type of PR, the issue it fixes, and the reason for the changes. It also references the related GitHub issue which is good practice.

Changes:

1. Security Issue:

   • The SQL query in the added files information_schema.result and information_schema.sql contains potential SQL injection vulnerabilities. Directly concatenating user input into SQL queries can lead to SQL injection attacks. To mitigate this risk, parameterized queries should be used to prevent malicious input from altering the query's logic.

2. Code Optimization:

   • The SQL query is duplicated in both information_schema.result and information_schema.sql. It would be better to have a single source of truth for the query to avoid redundancy and potential inconsistencies. Consider consolidating the query into a shared file and referencing it from both places to maintain consistency.

3. Code Readability:

   • The SQL query is quite long and complex, which may reduce readability and maintainability. Consider breaking it down into smaller, more manageable parts or adding comments to explain the purpose of each section for better understanding by other developers.

4. Code Formatting:

   • The added SQL query lacks a newline at the end of the file. It is recommended to add a newline character at the end of the file for better code formatting and to adhere to common coding standards.

Suggestions for Improvement:

1. Security Enhancement:

   • Refactor the SQL query to use parameterized queries or prepared statements to prevent SQL injection vulnerabilities. This can be achieved by using placeholders for dynamic values and binding parameters securely.

2. Code Refactoring:

   • Consolidate the duplicated SQL query into a shared file to avoid redundancy and ensure consistency across the codebase. This will make maintenance easier and reduce the chances of discrepancies.

3. Code Documentation:

   • Consider adding comments or documentation to explain the purpose of the SQL query, the tables involved, and the expected results. This will help other developers understand the query's intent and functionality.

4. Code Formatting:

   • Ensure that the added files follow consistent code formatting practices, including adding a newline character at the end of the file for better readability.

By addressing the security issues, optimizing the code changes, and enhancing code readability, the pull request can be improved to ensure a more secure and maintainable codebase.