fix(appium): appium symlink behavior across drivers/plugins installations

[KazuCocoa]

Proposed changes

This is related to #21664. I noticed this issue in https://github.com/appium/ruby_lib_core/actions/runs/20587570810.

The issue occurs in drivers when we install plugins, or plugins when we install drivers.

e.g.

appium driver install xcuitest
appium plugin install images  # then, the appium symlink in the node_modules in xcuitest is missing

Expected behavior is even after the plugin installation, the symlink to xcuitest should exist.

Types of changes

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

• Bugfix (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 not work as expected)
• Documentation Update (if none of the other choices apply)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• I have read the Contributing Guide
• I have signed the CLA
• Lint and unit tests pass locally with my changes
• I have added tests that prove my fix is effective or that my feature works
• I have added the necessary documentation (if appropriate)
• Any dependent changes have been merged and published in downstream modules

Further comments

If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...

[mykola-mokhnach]

do we need this import?

[KazuCocoa]

Yes, this is used to write some syntax for assertions. I assume we have this before...? since the type exists in the package.json already.