generate-proxy compatible with multiple appservices for one controller ?

Is there an existing issue for this?

• I have searched the existing issues

Is your feature request related to a problem? Please describe the problem.

For code organization purposes, we separate the methods of the same controller into several appservices.
For example:
Instead of having one service MailMessageService which contains: GetAsync() & UpdateAsync() methods
MailMessageService
----GetAsync()
----UpdateAsync()

We have 2 services GetMailMessageService which contains: GetAsync() and UpdateMailMessageService which contains: UpdateAsync()

GetMailMessageService
----GetAsync()

UpdateMailMessageService
----UpdateAsync()

We overrided the UrlControllerNameNormalizer as follows:

Configure<AbpAspNetCoreMvcOptions>(options =>
        {
            options.ConventionalControllers
            .Create(typeof(MyApplicationModule).Assembly, opts =>
            {
                opts.UrlControllerNameNormalizer = context => context.ControllerName?
                .IgnorePrefixes("Get", "Create", "Update", "Delete");
            });
        });

It works fine when it comes to deleting prefixes and having a well formed endpoint name, but when it comes to generating proxy (angular), it generates only one angular service MailMessageService (with prefix removed), instead of bot GetMailMessageService, UpdateMailMessageService .

Can we take advantage of the generate-proxy command for angular while maintaining consistency in the api endpoints but being able to split our appservices (by separating the CRUD methods for example)?

Describe the solution you'd like

I would like to have 2 different services (GetMailMessageService and UpdateMailMessageService) in the backend, with endpoints names overrided as follows :

Configure<AbpAspNetCoreMvcOptions>(options =>
        {
            options.ConventionalControllers
            .Create(typeof(MyApplicationModule).Assembly, opts =>
            {
                opts.UrlControllerNameNormalizer = context => context.ControllerName?
                .IgnorePrefixes("Get", "Create", "Update", "Delete");
            });
        });

And being able to generate 2 services in the front part, using generate-proxy command:
get-mail-message.service.ts
----getAsync()

update-mail-message.service.ts
----updateAsync()

Additional context

No response

Start by tracing the generate-proxy command's Angular service generation and how UrlControllerNameNormalizer is applied through AbpAspNetCoreMvcOptions. Compare the generated service grouping with the separate GetMailMessageService and UpdateMailMessageService examples. Done means both backend appservices retain normalized endpoints while generate-proxy produces separate Angular services for them.