[Project Monitors] Gap between UI configuration for browser monitors and push

[paulb-elastic]

Similar to what’s needed for the lightweight monitor gap, we need to ensure that configuration options that can be defined in the UI for browser monitors, can also be done for project monitors.

ACs:

• Identify the configuration options available in the UI
  • Note that Use project monitors to add APM configuration #656 has been raised for the APM service name specifically, but there will be others
• Implement these for Project Monitors (push)

[vigneshshanmugam]

Dominique has brought up in the other issue that we dont support some of the specific options that are available in the UI and Heartbeat and not as part of synthetics.config.ts. Some of the items are

1. enabled | screenshots - Supported on individual monitors via monitor.use but not in config.
2. params|playwright_options - Supported via top level fields in config and not under monitor to avoid duplication
3. tags - Uniquely used as filtering the journey run. So have to rename or treat it differently in the config.

More details on this comment - #649 (comment) and #649 (comment)