Make usage data billing filtering extensible in SetUsageDataBillingFilters

[miljance]

What & why

SetUsageDataBillingFilters on table 8059 "Subscription Line" filtered "Usage Base Pricing" with a bounded SetRange from "Usage Quantity" to "Unit Cost Surcharge". That upper bound assumed enum 8007 "Usage Based Pricing" ends at "Unit Cost Surcharge", so any custom value a partner adds above it fell outside the range and was silently excluded — potentially returning an empty Usage Data Billing recordset. There was also no hook for partners to adjust the applied filters.

This change:

• Replaces the bounded SetRange with SetFilter("Usage Base Pricing", '>=%1', Enum::"Usage Based Pricing"::"Usage Quantity"). This preserves the original behavior (still excludes "None") while remaining open-ended, so custom enum values are included instead of dropped.
• Adds integration event OnAfterSetUsageDataBillingFilters(var UsageDataBilling; SubscriptionLine; BillingFromDate; BillingToDate) at the end of the procedure so subscribers can refine the filters without overriding the base logic.

Linked work

Fixes #9223

How I validated this

• I read the full diff and it contains only changes I intended.
• I built the affected app(s) locally with no new analyzer warnings.
• I ran the change in Business Central and confirmed it behaves as expected.
• I added or updated tests for the new behavior, or explained below why none are needed.

What I tested and the outcome

Change is a small, self-contained filter adjustment plus a new integration event publisher. The new filter >=%1 from "Usage Quantity" is logically equivalent to the previous "Usage Quantity".."Unit Cost Surcharge" range for all shipped enum values (ordinals 1–3), and additionally includes any partner-added values (ordinal ≥ 4) that the old bounded range excluded; "None" (ordinal 0) remains excluded.

Risk & compatibility

Low. For the enum values that ship today the filter result is unchanged. The only behavioral difference is that "Usage Base Pricing" values above "Unit Cost Surcharge" are now included rather than excluded — which is the intended fix. The new OnAfterSetUsageDataBillingFilters event is additive.