fix: disable search for rental Actors

[MQ37]

closes #135

[jirispilka]

Thank you!

However, I would simplify the implementation and take a different approach—please see my comments.

There’s a major issue, though: What if the user has rental Actors?
We should also search for Actors the user is renting. For that, we’d need to access the database... because this server can also be run locally

If we want to support this in actors-mcp-server, we’ll need to introduce a new API.

FYI @mtrunkat

[jirispilka]

I discussed this with Mara. We should also return rental Actors for a particular user.

However, since the Actors MCP server can be run locally without a database connection:

• For local deployments, we won’t return rentals at all.
• For remote deployments, we can pass a MongoDB connection to the Actors MCP server and handle users rentals there.

Later on, we can introduce an API to provide this functionality. However, I'm not sure if such an API would be needed for anything else. I'll share this in Product Insights.

[MQ37]

@jirispilka @MichalKalita updated to logic, we are now passing list of users rented Actor IDs from apify-mcp-server to the search store tool call and handling that here without passing any mongo connection (I don't think we should do this in open source repo and internal MongoDB structure should remain hidden). If list of rented Actors is passed we filter out all no-rented rental Actors, if not then we just filter out all rental Actors.

please see #80

[jirispilka]

Nice, it is better to pass rented Actors than the mongo connection. Cool!