[Bug]: Inconsistent REST Path Validation Between `init` and `configure`

## Expected:
Both should behave the same, either reject or normalize consistently.

```
# This silently succeeds (prepends /):
dab init --database-type mssql --connection-string "test" --rest.path "noslash" --config test.json

# This correctly fails:
dab configure --runtime.graphql.path "noslash"
# fail: Path must start with a '/'
```

Start with the `dab init` and `dab configure` command entry points and reproduce both path-validation behaviors from the issue. Trace where `rest.path` and `runtime.graphql.path` are validated, then run the relevant CLI tests or commands to confirm both reject or normalize paths consistently.

Written by the indexing model from the issue text.