docs(specs): document scheduling support in application service spec

[olivermeyer]

Why?
PR #479 added first-class scheduling support (due_date/deadline) to application run submission, but the SPEC-APPLICATION-SERVICE.md was not updated to reflect these changes.

How?
Expanded the application_run_submit signature with all current parameters including due_date and deadline and added the previously undocumented application_run_submit_from_metadata method.

[Copilot]

Pull request overview

Updates the application service specification to reflect first-class scheduling support (due_date/deadline) and the current run submission API surface.

Changes:

• Expanded application_run_submit signature and argument documentation to include scheduling and other current parameters.
• Documented application_run_submit_from_metadata in the public API section.
• Added scheduling date validation rules to the validation section.

Comments suppressed due to low confidence (1)

specifications/SPEC-APPLICATION-SERVICE.md:346

• There’s no blank line between the end of application_run_submit_from_metadata and the next method definition inside the fenced Python example (pass is immediately followed by def application_run_download). Adding a blank line would keep the interface example consistently formatted and easier to read.

        pass
    def application_run_download(

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ All tests successful. No failed tests found.
see 7 files with indirect coverage changes

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud