Set upper pulpcore bound to 3.130, to align with other Pulp plugins

[ianballou]

Our plugin doesn't need to be so strict about the upper bound, Pulpcore doesn't change that often. Instead they follow a breaking change schedule. If you look at other plugins, right now you'll see an upper bound of 3.130. We should do the same. It is tedious to have to do these y-release bumps so often.

For example: https://github.com/pulp/pulp_container/blob/54b396628fe36de29909ddd95f8a41c3486fd924/pyproject.toml#L27

See https://pulpproject.org/pulpcore/docs/user/learn/pulp-versioning/

After this is out, I'd like to request another release. We are aiming to go for Pulpcore 3.108 after all, since Pulp has come out with it since we've been prepping to upgrade Pulp. Haven't done enough work to justify not going to 3.108.

📜 Checklist

• Commits are cleanly separated with meaningful messages (simple features and bug fixes should be squashed to one commit)
• A changelog entry or entries has been added for any significant changes
• Follows the Pulp policy on AI Usage
• (For new features) - User documentation and test coverage has been added

See: Pull Request Walkthrough

[Odilhao]

Can you kick one release for us @evgeni ? Looks like I don't have permission to run that.

[evgeni]

Running.

[ianballou]

Thanks!