autoclass: Method order incorrect if automethod is used

[TTSPhilipp]

Describe the bug

If automethod is used in autoclass, then the method is always placed at the top, regardless of which option was selected for member-order.

My expectation:
The Call(...) method should be displayed at the place where the original Call method would have been, since bysource was selected for member-order.

An alternative would be if I could set a parameter for automethod to define where the method should be displayed.

It would also be okay if the method is simply appended below.

How to Reproduce

.. autoclass:: MyClass
    :special-members: __init__
    :member-order: bysource
    :members:
    :no-undoc-members:
    :exclude-members: Call

    .. automethod:: Call(...)

Environment Information

Platform:              win32; (Windows-10-10.0.26100-SP0)
Python version:        3.11.9 (tags/v3.11.9:de54cf5, Apr  2 2024, 10:12:12) [MSC v.1938 64 bit (AMD64)])
Python implementation: CPython
Sphinx version:        8.1.3
Docutils version:      0.21.2
Jinja2 version:        3.1.4
Pygments version:      2.18.0

Sphinx extensions

["sphinx.ext.autodoc"]

Additional context

No response

[electric-coder]

My expectation:
The Call(...) method should be displayed at the place where the original Call method would have been, since bysource was selected for member-order.

In fact it shouldn't, those options have always been independent in that members automatically included by the enclosing directive precede those that are explicitly declared in its scope.

This report (that isn't a bug but an FR) doesn't include a MRE because it lacks the necessary Python declarations and it also lacks a screenshot to show unambiguously what the problem is.