Backend: Claims request decision job id fix

[aherzberg]

Description

the new Lighthouse endpoint returns a boolean success rather than the job id. FE doesn't use the id so for backwards compatibility we're keeping the Job id field and just put string of success or failed for debugging purposes.

Dependent Issue

department-of-veterans-affairs/va-mobile-app#0000 or N/A

Test users

vets.gov.user+000@gmail.com

Acceptance Criteria

• ...
• It logs its progression through the 'happy path' or helpful error details.
• I tested the feature on staging and could demo it if asked.
• Public Ruby API methods have Yardoc comments.
• The OpenAPI documentation is up-to-date.

[TKDickson]

Adding a comment (supplementing the documentation from 6 days ago when I added the blocking ticket) - this ticket is blocked by #6010, which is blocked by an external team's work.

[TKDickson]

Even though it's a larger time sink in terms of data prep (that I will have to repeat after the blockers around #6010 are resolved), I don't have anything else on my list this morning so pulling this out of the blocked column and taking a look.

[TKDickson]

New response:

{
	"data": {
		"jobId": "success"
	}
}