Route template parameters order cannot be changed even with ODataAttributeRoutingAttribute

Assemblies affected
ASP.NET Core OData 8.0.11

Describe the bug
Refering to this post from @xuzhg
https://stackoverflow.com/questions/72182707/odata-v7-8-should-composite-keys-be-in-alpha-order-or-haskey-when-key-value

Or you can use the attribute routing. In attribute routing, you can set any order in the route template.

I tried with ODataRoutingSample and it didn't work (or I didn't understand something)

Reproduce steps

1. Open the AspNetCoreOData solution
2. Edit ODataRoutingSample.Controllers.PeopleController to inherit from ODataController (which has a ODataAttributeRouting attribute)
3. Launch the ODataRoutingSample project

This request works :
http://localhost:64771/People(FirstName='Magazine',LastName='Jingchan')

But this request does not work (404) :
http://localhost:64771/People(LastName='Jingchan',FirstName='Magazine')

Additional context
I think it is important to allow the key parameters to be specified in any order.
I know you can enforce it with the Order property in the model configuration, but since query parameters in MVC can be set in any order, same is expected for the key parameters from the route template.

Start by opening the AspNetCoreOData solution and the ODataRoutingSample.Controllers.PeopleController described in the reproduction steps. Run the sample and compare the two People requests with reversed key parameters, then trace the ODataAttributeRouting behavior. Done means both URL parameter orders route successfully instead of the reversed order returning 404.