Move yaml import to top-level for better code organization

[cursor]

Summary

Move yaml import from inside the fillPhoneNumber() method to top-level imports in linkedin.py.

Changes

• Moved import yaml from line 380 (inside method) to line 10 (top-level imports)
• Removed inline import statement from the exception handling block in fillPhoneNumber() method

Benefits

• Better code organization: All module dependencies are now visible at the top of the file
• Improved performance: Eliminates overhead from repeated import checks if the method is called multiple times
• Follows best practices: Adheres to PEP 8 and Python conventions for import organization
• Cleaner code: Reduces try-except complexity by separating import concerns from logic

Testing

• Syntax validation passed with python3 -m py_compile
• No functionality changes, only import reorganization