added a comment - - edited
It is not as simple as Frans said, or at least I think so. Snippet from docs:
NoContextMenu the widget does not feature a context menu, context menu handling is deferred to the widget's parent.
PreventContextMenu the widget does not feature a context menu, and in contrast to \c NoContextMenu, the handling is
not deferred to the widget's parent. This means that all right mouse button events are guaranteed to be delivered to the
widget itself through mousePressEvent(), and mouseReleaseEvent().
DefaultContextMenu the widget's QWidget::contextMenuEvent() handler is called.
ActionsContextMenu the widget displays its QWidget::actions() as context menu.
CustomContextMenu the widget emits the QWidget::customContextMenuRequested() signal.
I understand that DefaultContextMenu , ActionsContextMenu or CustomContextMenu policies only define what should happen after context menu event is triggered, i.e. is contextMenuEvent called, is context menu automatically build from widget actions or is customContextMenuRequested signal emitted. The policy does not have effect on how the context menu event is triggered. "Actions" in options menu exist in order that context menu event can be triggered. I agree it is silly, but especially in keypad navigation devices there is currently no other way to launch the context menu than Options menu item called "Actions". If we took that item away, how would customContextMenuRequested signal emitted?
In touch screen devices also long tap invokes the context menu, so in theory we could remove the whole "Actions" item for touch screens. But as far as I remember it correctly S60 style guide (for 3.1 - 5.0?) says that all context menu items should be available also in Options menu (preferably not in the submenu). Also in case when ActionsContextMenu policy is used, we could check that if widget does not have any actions associated to it, the "Actions" item is not shown. However for DefaultContextMenu and CustomContextMenu we can't do that kind of check, but we should have some possibility to trigger context menu event. In S60 middle softkey or select key is used to launch context menu, however in Qt this event is already used to switch to edit mode.
As a summary, I think the "Actions" is in options menu by default but I agree it is silly.