Based on #22582

The planning is like that:

• We will implement an alternative object mapper based on an open-source library (haven't decided yet, open to suggestions)
• We won't remove the Volo.Abp.AutoMapper package, so this is a backward-compatible change. However, if you continue to use it, you should handle the licensing yourself. We will depend on the latest free version as long as possible (it is version 14.0.0 at the moment). If we have any issue (like .NET 10.0 incompatibility), we have to upgrade to 15.0.0 or a newer version, which requires a license code.
• We will change all of our modules' code to use the new mapper implementation, so none of ABP Platform's modules will require AutoMapper.
• Extract the AutoMapper part of the Object to Object mapping documentation (https://abp.io/docs/latest/framework/infrastructure/object-to-object-mapping) to a new document (like https://abp.io/docs/latest/framework/infrastructure/object-to-object-mapping/automapper).
• Document the new library integration (like https://abp.io/docs/latest/framework/infrastructure/object-to-object-mapping/new-library-name)
• Update all documentation (tutorials, etc) to use the new mapping library
• Change code generation logic for ABP Suite and ABP Studio to work with the new mapping library. No need to provide both of the options, because our modules will use the new library, and the solution will already have that dependency. But, in any way, it would be good to think about the effort of supporting both of the libraries for a few versions.
• Think about any other stuff we need to consider on this change