CHORE: Convert ServiceRunner to Kotlin

[lijamie98]

Description

• Convert ServiceRunner from Java to Kotlin, maintaining full functional parity and Java interoperability
  • Refactored from a Java class with static methods to a Kotlin object (singleton pattern)
  • Updated imports to use Kotlin top-level functions for reference server and wallet server initialization
• Add VS Code IDE configuration files (.vscode/launch.json, .vscode/settings.json, .vscode/tasks.json)
  • .vscode/launch.json: Pre-configured launch configurations for all Anchor Platform services and test profiles (18 configurations total)
    • Core services: SEP Server, Platform Server, Custody Server, Event Processing Server, Stellar Observer (Horizon and Soroban variants)
    • Reference servers: Kotlin Reference Server, Wallet Reference Server
    • Test profiles: 10 different test profile configurations (default, custody, deployment, RPC variants, etc.)
    • Docker dev stack configuration
  • .vscode/settings.json: Java development settings (note: contains empty strings for java.jdt.ls.java.home and java.debug.settings.vmArgs which may need to be configured per developer)
  • .vscode/tasks.json: Empty file for future task definitions
• Remove .vscode from .gitignore to allow committing VS Code configuration files
• Make scripts/docker-start.sh executable (set executable file permissions)

Context

• VS Code Java Extension does not work well with Java classes importing Kotlin classes. Converting ServiceRunner.java to Kotlin works around the issue.

Testing

• ./gradlew test - All existing tests pass

Documentation

N/A

Known limitations

NA

[cursor]

This PR is being reviewed by Cursor Bugbot

Details

You are on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle.

To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.

[cursor]

Missing TEST_PROFILE_NAME environment variable in launch configuration

Medium Severity

The "Test Profile: host.docker.internal" launch configuration doesn't set the TEST_PROFILE_NAME environment variable. Unlike other test profile configurations (e.g., "default-horizon", "custody") that explicitly set TEST_PROFILE_NAME in their env block, this configuration is missing it entirely. Without TEST_PROFILE_NAME set to host-docker-internal, the configuration will run the default profile instead of the intended host-docker-internal profile, causing unexpected behavior for developers who expect the configuration name to match the actual test profile being executed.