Add examples for try it out, #PG-5178

[lachiebol]

Description

To get updated specs:

core:run-scheduled-tasks "Piwik\Plugins\OpenApiDocs\Tasks.generateConfiguredPluginSpecs" --force

Then you can verify in the UI tab

Issue No

Steps to Replicate the Issue

Checklist

• [✔/✖] Tested locally or on demo2/demo3?
• [✔/✖/NA] New test case added/updated?
• [✔/✖/NA] Are all newly added texts included via translation?
• [✔/✖/NA] Are text sanitized properly? (Eg use of v-text v/s v-html for vue)
• [✔/✖/NA] Version bumped?
• [✔/✖/NA] Documentation updated?

[lachiebol]

New examples, have done a quick sense check. But if anything doesn't look right let me know

[lachiebol]

If it's a complex array type I'm just leaving it for now. When I implement POST this can be changed

[lachiebol]

Same here: will remove this logic when adding POST. At the moment it prevents complex param examples from coming through

[lachiebol]

@AltamashShaikh Will address these concerns in POST request PR

  - Blocking: Generic typed arrays with non-scalar items are now documented as arrays of strings. In Annotations/AnnotationGenerator.php:488, array<int, VisitDescriptor> and
    array<int,array<string,mixed>> are normalized to array, then their subtype is passed through getOpenApiTypeFromPhpType() at Annotations/AnnotationGenerator.php:491. Unknown
    subtypes fall back to string, so a real API like /home/lachlan/matomo-code/matomo_5x-dev/plugins/PrivacyManager/API.php:82 with @param array<int, VisitDescriptor> $visits gets
    emitted as an array of strings. Before this branch, those generic arrays stayed untyped; this change makes the schema actively wrong.
  - Medium: A noticeable part of the new config payload is unreachable, so the branch does not actually add examples for many of the complex parameters it targets.
    normaliseConfiguredParameterExample() explicitly rejects associative and nested arrays at Annotations/AnnotationGenerator.php:653, and the test suite codifies that behavior at
    tests/Unit/AnnotationGeneratorTest.php:1300. But the new config adds several such values, for example config/ParameterExamples.php:24, config/ParameterExamples.php:113, config/
    ParameterExamples.php:158, and config/ParameterExamples.php:191. Those entries will never surface in generated docs, so the branch only improves simple examples, not the complex
    cases it now enumerates.

[AltamashShaikh]

ActivityLog, before schedule task run
period and date are being filled as null, which throws an error

After schedule task run, fixes the issue 👍