NEW: KEY_MODULE-filed rights now group with their target module and sort next to it

[hregis]

Rights declared by a module but filed into another module's section of the permission grid (DolibarrModules::KEY_MODULE) previously kept the declaring module's own family/module_position, opening a second, misplaced section instead of merging with the target module's native rights. User::loadRights() and UserGroup::loadRights() also indexed such rights under the display module column instead of module_origin, so hasRight() could never resolve them under the module that actually declared and controls them.

• insert_permissions() now resolves family/module_position from the target module (getModuleInfoByRightsClass(), cached) when KEY_MODULE differs from the declaring module.
• loadRights() (User and UserGroup) indexes $user->rights by module_origin when set, so hasRight() checks against the declaring module regardless of where the right is displayed.
• New rights_def.sort_order column + DolibarrModules::KEY_SORT_ORDER let such a right sort right next to a specific native right of the target module (set to that right's id) instead of always trailing the whole section. module_position can't carry this: it's a per-module value that user/perms.php actively normalizes back to the module's own position on every page load.
• user/perms.php, user/group/perms.php, admin/perms.php: sort by sort_order (falling back to id, unchanged for every existing right), tooltip and a small badge now show the actual declaring module for such rights.