Added support for searching projects

[pcodding]

Description

Added a new search_projects action to the Linear Action Package that enables searching for projects by name, team, and initiative. This feature enhances the package's capabilities by providing project management functionality alongside the existing issue management features.

Key additions include:

• New search_projects action with filtering capabilities
• Project-related models for type safety and validation
• Proper handling of empty string inputs
• Post-query filtering for team names due to Linear API limitations

How can (was) this tested?

The following test scenarios were implemented:

• Search projects by name
• Search projects by team name (post-query filtering)
• Search projects by initiative
• Test empty string handling in filter options
• Test pagination limits
• Test ordering (createdAt, updatedAt)

Test using the example inputs in devdata/input_search_projects.json with different combinations of:

• Project name filters
• Team name filters
• Initiative filters
• Result limits
• Ordering options+

Screenshots (if needed)

N/A

Checklist:

• I have bumped the version number for the Action Package / Agent (1.1.0)
• I have performed a self-review of my own code
• I have updated the CHANGELOG.md file in correspondence with my changes
• I have added tests that prove my fix is effective or that my feature works

[tonnitommi]

• We should use this update to add external access information to package yaml, as we need this for all gallery actions.

• Maybe also add one query example with projects to README?

[mikahanninen]

We had a call with Kari and there was a decision to place EAI rules between "dependencies" and "packaging". Refer to Browsing/Perplexity/Serper for an example.

Otherwise LGTM

[pcodding]

Fixed the location of the EAI definitions. Let me know if this is good to merge.