TJK: custom roles adjustments

[MatiasArriola]

✨ Description of Change

Link to GitHub issue or Jira ticket: https://app.clickup.com/t/869da29v7

Description:

This PR aligns legacy inventory/product actions with the custom role permissions matrix.

It fixes two related issues:

• custom-role users could be allowed by backend policy but still hit a client-side Access denied alert from legacy g:link authorization
• legacy product and inventory views were still showing actions that should be hidden for custom roles

Changes

• allow Facility Storekeeper and Regional Warehouse to complete the record stock workflow end to end
  • inventoryItem.showRecordInventory
  • inventoryItem.saveRecordInventory
  • recordStockApi.saveRecordStock
• allow Regional Warehouse to create stock requests consistently with the matrix
  • stockMovement.createRequest
  • stock-request API access remains scoped to stock requests only
• update shared g:link authorization to honor custom role policy before applying legacy manager/admin/superuser link disabling
• add custom view tags for:
  • record stock visibility
  • outbound movement visibility
• hide legacy UI actions according to the matrix
  • hide Edit product for roles without product management access
  • hide Manage stock lists for roles without stocklist management access
  • hide outbound transfer actions for roles without outbound permissions

Why

The custom permissions matrix is enforced in CustomRolePolicyService, but several legacy GSPs were still using older role assumptions in the UI.

That created two bad outcomes:

• actions like Record stock were technically allowed but blocked in the browser before navigation
• actions like Edit product were visible even though the matrix says they should not be accessible

This PR makes the visible actions and actual route authorization consistent.

Expected behavior after this change

• Facility Storekeeper

  • can use Record stock
  • can create stock requests
  • does not see Edit product
  • does not see Manage stock lists

• Regional Warehouse

  • can use Record stock
  • can adjust stock
  • can create stock requests
  • does not see Edit product
  • does see Manage stock lists

Assumed "Record stock" is allowed because it is an inventory write action, like adjust stock.