feat: Linkup intergrate

[raywhoelse]

Description

Describe your changes in detail.

Motivation and Context

close #1345

• I have raised an issue to propose this change (required for new features and bug fixes)

Types of changes

What types of changes does your code introduce? Put an x in all the boxes that apply:

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds core functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation (update in the documentation)
• Example (update in the folder of example)

Implemented Tasks

• Subtask 1
• Subtask 2
• Subtask 3

Checklist

Go over all the following points, and put an x in all the boxes that apply.
If you are unsure about any of these, don't hesitate to ask. We are here to help!

• I have read the CONTRIBUTION guide. (required)
• My change requires a change to the documentation.
• I have updated the tests accordingly. (required for a bug fix or a new feature)
• I have updated the documentation accordingly.

[Wendong-Fan]

thanks @raywhoelse ! There are some minor issues with the docstring format that need to be fixed. For this search function, I feel it's not necessary to add four additional helper functions. While making the code more modular has its benefits, in this case, it adds redundancy without enough value to justify it. WDYT?

[Wendong-Fan]

Hi @raywhoelse , Please remember to run poetry.lock if you've updated the pyproject.toml file, also add unit test

Thanks @liuxukun2000's review, please kindly follow our Code Review Checklist when approving PRs, the check for this PR is failing. Code review approvals should be even stricter than writing code yourself. Your code undergoes review before merging, but if you approve a PR, it could be merged directly into our main branch, leaving no room for errors.