Admin actions: use SortedDict instead of dict for predictable actions order

[Mikhail Korobov]

I think the ability to define order of actions is a nice usability feature. The order of admin actions in drop-down menu now depends on internal python dict representation. If in get_actions function we use

actions = SortedDict()

instead of

actions = {}

actions wil have fixed order: the ones defined first will come on the top of the list. For example, if we define some custom actions using

actions=['action1', 'action2']

action1 will be before action2 in drop-down. For reverse order we will be able to write

actions=['action2', 'action1'].

[Jacob]

(In [10408]) Made a bunch of improvements to admin actions. Be warned: this includes one minor but BACKWARDS-INCOMPATIBLE change.

These changes are:

• BACKWARDS-INCOMPATIBLE CHANGE: action functions and action methods now share the same signature: (modeladmin, request, queryset). Actions defined as methods stay the same, but if you've defined an action as a standalone function you'll now need to add that first modeladmin argument.
• The delete selected action is now a standalone function registered site-wide; this makes disabling it easy.
• Fixed #10596: there are now official, documented AdminSite APIs for dealing with actions, including a method to disable global actions. You can still re-enable globally-disabled actions on a case-by-case basis.
• Fixed #10595: you can now disable actions for a particular ModelAdmin by setting actions to None.
• Fixed #10734: actions are now sorted (by name).
• Fixed #10618: the action is now taken from the form whose "submit" button you clicked, not arbitrarily the last form on the page.
• All of the above is documented and tested.

[Jacob]

Milestone 1.1 deleted