[RUN ALL RSPEC] [RUN AS-IF-FOSS] Resolve "Filter usage_data payload considering metric category"

What does this MR do?

It adds new service that is responsible for filtering Service (aka Usage) Ping payload based on instance settings. This service is not yet put to use anywhere, that would be objective of follow up MR

Filtering rules are as follows:

1. If single users consent is required User.single_user&.requires_usage_stats_consent? == true send no data
2. For a free user, when License.current is blank when usage ping enabled send: Standard, Subscription, Optional, and Operational metrics
3. For a free user, when License.current is blank when usage ping is disabled don't send any data
4. For a customer, when License.current is not blank. When usage ping enabled and operational data enabled(License.current.usage_ping? ==. true) send: Standard, Subscription, Optional, and Operational metrics
5. For a customer, when License.current is not blank. When usage ping enabled and operational data disabled(License.current.usage_ping? == false) send: Standard, Subscription, and Optional metrics
6. For a customer, when License.current is not blank. When usage ping disabled and operational data enabled(License.current.usage_ping? ==. true) send: Standard, Subscription, and Operational metrics
7. For a customer, when License.current is not blank. When usage ping disabled and operational data disabled(License.current.usage_ping? == false) don't send any data.

Screenshots (strongly suggested)

Does this MR meet the acceptance criteria?

Conformity

• I have included changelog trailers, or none are needed. (Does this MR need a changelog?)
• I have added/updated documentation, or it's not needed. (Is documentation required?)
• I have properly separated EE content from FOSS, or this MR is FOSS only. (Where should EE code go?)
• I have added information for database reviewers in the MR description, or it's not needed. (Does this MR have database related changes?)
• I have self-reviewed this MR per code review guidelines.
• This MR does not harm performance, or I have asked a reviewer to help assess the performance impact. (Merge request performance guidelines)
• I have followed the style guides.
• This change is backwards compatible across updates, or this does not apply.

Related to #333681 (closed)