Updated User-Agent strings

[marekrost]

Updated User-Agent strings with more recent ones to prevent LinkedIn WAF immediately catching on and showing CHALLENGE.

[EseToni]

Hey @marekrost ! Thanks a lot for the contribution — totally see where you're coming from.

The updated headers make sense and could definitely help reduce the chances of hitting the challenge. That said, I think we can approach this in a cleaner way: instead of merging this directly into the main branch, we could create a dedicated branch where we start implementing changes like these — including potential improvements discussed in the issue #1, such as switching to GraphQL and mimicking LinkedIn’s frontend behavior more closely.

This way, we avoid breaking compatibility for users who are currently syncing their cookies with browser headers as-is, while still experimenting with better long-term solutions.

Let me know what you think — happy to spin up a branch and collaborate there!

[marekrost]

If you don't mind I would like to have two:

1. staging or release-candidate / whatever for this commit, and a few more, where i'm exposing more internals to public facing functions (for example get_feed_posts() to permit non-chronological fetch.

2. refactor / graphql / whatever for the rewritten project.