#15 - Productionize response from ChatGPT

[idjevm]

What does this pull request aim to achieve?

• Clean up / refactor and restructure the swarm-rest-api as well as continue the work from @Clue355 on issue 13
• Refactored to use Java Records to be more easily deserialize the response so later it will be easy to persist when we start doing that work
• created a responseJsonStructure which should be what we expect from ChatGPT.
• Refactored from Carlos' work to use HttpClient as it is simpler

Now we are getting the follow response ->

I know a few things can be changed, but those can be on follow up small issues, and small PRs, so we can move past this step of getting the first setup done.

To look at my changes directly look into my commit here

What is left to do from this?

• Fix up unit test
• handle all TODOs left on the comments
• Some more refactoring
• more refactoring and other changes that can be done in following issues / PRs.

Please be concise and link any related issue(s): closes #15 closes dup #14 closes #13 from @Clue355

Please do NOT submit this PR if you have not done the following:

• [x] The name of this PR is #issueNumber - short description
• [x] I have filled the issue number in the above lines to link any related issue(s)
• [x] I have checked that no one else is working on similar changes.
• [x] The name of this branch is: issueNumber-short-description, and that the branch is created in a cloned version of this repo, not a forked repo.
• [x] This branch is rebased/merged with the latest staging
• [x] There are no merge conflicts.
• [x] On the right-hand side of this PR, I have linked the appropriate projects under Projects, requested at least 2 reviewers under Reviewers, and I have assigned this PR to myself & others needed under Assignees

[idjevm]

@MelisaIm / @lindentree I know that we are not able to add more than one person so I am tagging you here for you all to take a look also and leave any comments.

Reason this PR is big is because it is bringing the changes that @Clue355 had but you can look at the changes directly by seen my commit.

I will work with Carlos to get his PR open so I can use that as a base and then this one will be much cleaner PR :)

[Clue355]

looks like the test failed in the project. Edit that to make it work

[idjevm]

test is failing

I actually left a comment that I will not be handling tests on this PR but will need to make a separate PR for following TODOs & tests - I might extend from this branch so that way it doesn't become too big, but yeah tests will be handled in a separate PR / branch.

[idjevm]

LGTM! Maybe it would be better to have @fsantamaria1’s PR merged first though, to spread out the contributions.

Yup, I asked him to do that so I am going to hold off for his PR to be merged before merging this one.