Align 'allowOnAccountFreeze' routes with permissions from Backend

## What is the problem?
* some routes are allowed on account freeze nsf. which is currently managed by the meta tag 'allowOnAccountFreeze' in the routes.

## What is the impact?
* need to make it more backend driven, by mapping with the permissions array from backend.

## Proposed solution
* need to figure


Start by locating the routes that use the allowOnAccountFreeze meta tag and the backend permissions array referenced in the issue. Determine how those values should map, then verify that account-freeze route access follows the backend permissions; no specific files or tests are named in the issue.

Written by the indexing model from the issue text.