fix: validate the effective configuration (#2352)

Fixes an issue that we validate the original configuration coming from a
request, but not the effective configuration that is created by merging
the configuration profile with the request configuration.

Tested with a custom version of field-service-routing in the sandbox
environment.

Author: rsynek

model/rest/src/main/java/ai/timefold/solver/model/rest/impl/AbstractModelAPIResource.java

@@ -656,12 +656,13 @@ public Multi<Metadata<Score_>> streamMetadata(
     @Produces(MediaType.APPLICATION_JSON)
     public ValidationResult<ValidationIssue_> getValidationResult(
             @Parameter(description = "Unique identifier of the schedule", required = true) @PathParam("id") String id) {
-        ValidationBuilder validationBuilder = new ValidationBuilder();
-        ModelRequest<ModelInput_, ModelConfigurationOverrides_> modelRequest = storageService.getModelRequest(id);
-        if (modelRequest.modelInput() == null) {
+        ModelInput_ modelInput = storageService.getModelInput(id);
+        if (modelInput == null) {
             throw new ItemNotFoundException(ErrorCodes.STORAGE_NO_JOB_FOUND, id);
         }
-        modelValidator.validate(validationBuilder, modelRequest.modelInput(), modelRequest.getModelConfig());
+        var modelConfig = Configuration.getSafeModelConfig(storageService.getConfiguration(id));
+        ValidationBuilder validationBuilder = new ValidationBuilder();
+        modelValidator.validate(validationBuilder, modelInput, modelConfig);
         return validationBuilder.build();
     }