Normalize Assets Manager current-page exception IDs

[mehul0810]

Finding

Assets Manager current-page exceptions are saved from POST payload values, while runtime checks compare them against get_queried_object_id() using strict comparison.

Impact

A rule such as “disable everywhere, but enable on current URL” can fail when the saved current-page ID is stored as a string and the runtime current object ID is an integer. That makes per-page asset exceptions unreliable.

Suggested implementation

• Cast current-page IDs to integers before persisting them in perform_assets_manager_options.
• Normalize existing saved current arrays when reading or updating rules.
• Use strict comparisons after both sides have the same type.
• Preserve the existing option key and nested array contract.

Acceptance criteria

• A current-page exception works after saving and reloading the page.
• Existing saved current-page exceptions continue to work after normalization.
• Disabling everywhere with a current-page exception still disables the asset on other pages.
• Add regression coverage around current-page exception save/read behavior.

[mehul0810]

Completed in PR #98 against release/1.6.0. Assets Manager current-page exception IDs are normalized for legacy and current data shapes.