eigen: Add 3.4.90-unstable version

[AbrilRBS]

After discussing with the team, and after checking with upstream regarding the issues that arise from the lack of updates in https://gitlab.com/libeigen/eigen/-/issues/2907#note_2687977253, we have decided to add a new version with the latest commit available as of today.

The 3.4.90 version tag comes from the reported version in CMake https://gitlab.com/libeigen/eigen/-/blob/c487a4fe9eab5836330246b992fe7c17c06d6726/Eigen/src/Core/util/Macros.h#L22, even though it looks like the next release will be 5.x

The version is also marked as a pre-release, so by default users that have a version range won't resolve to this pre-release unless:

They specify it in the version range itself, with self.requires("eigen/[>=3 <4, include_prerelease]"), they add the core.version_ranges:resolve_prereleases=True core conf to their global.conf file, or they explicitly pin the version in their requires statement.

This commit has been tested with the new 1.22.2 onnxruntime (PR will follow to add the version) and pcl, as we have gotten reports that newer versions of eigen were needed for both of them.

This PR also removes support for some of the old eigen releases. Note that:

• This only means that we won't publish new changes to the recipes of those versions, but they will still be available for users to consume in the conancenter remote.
• Only 1 recipe uses a removed version, but this is a Conan 1 reciep that has not seen updates in years

Some more info can also be found in the comments of #28161

Closes #28161
Closes #28159
Closes #26435

[jcar87]

Some notes from me:

• Our goals are that the following version ranges always resolve to an actual release, and not to a dated commit on the main branch.

eigen/[*]
eigen/[>=3.4 <4]
eigen/[>=3.4]

The - in the version string guarantees that it wont be the case by default

• 3.4.90 is used because that's the version those commits report
• There are NO guarantees that this is backwards compatible with 3.4.0 - that is, there are breaking changes, we don't know which, so it may or it may not work
• If in the future there is another 3.4.90-unstable pointing to a more recent commit, no guarantees that is compatible with the previous commit either

In Conan Center, encoding a dependency on this version:

• is allowed when 3.4.0 does not work, e.g. onnxruntime
• will not be allowed when 3.4.0 is known to work for most configurations. For this case, users can use it at their own risk with [replace_requires] if they need to use this version