feat: Update swagger.yaml to improve descriptions and add format spec

[iamnivekx]

#67

[ilkamo]

@sssionggg @0xYankee-Raccoons @cmoutafidis could you please take a look at this? It’s a small change, but it improves the generated code from the OpenAPI schema, especially for strongly typed languages like Go.

@iamnivekx proposed to extend the main schema with the format field for certain integer properties to ensure the correct types (e.g., uint64) are generated. Without specifying the format, codegen tools default to a generic int, which can lead to type mismatches or overflows in some environments.

This will be super useful for the future support of https://github.com/ilkamo/jupiter-go as we use the OpenAPI schema to generate the right types.

[0xYankee-Raccoons]

hey, commented the correct sizes

[0xYankee-Raccoons]

also, after changing the schema, please run npm run build to generate with the new schema

[iamnivekx]

@0xYankee-Raccoons
Thanks for the feedback! I've implemented the suggested changes

[0xYankee-Raccoons]

@iamnivekx need you to run npm run build to generate with the new schema

[iamnivekx]

I’ve already run npm run build, but there doesn’t seem to be any changes. Could you please check if the schema was updated correctly or let me know if there’s anything else I should do?

[0xYankee-Raccoons]

let's close this PR @iamnivekx @ilkamo, we have discussed and will be using the schema from https://dev.jup.ag/docs/api/swap-api (as the aim of the schema in dev docs will be the most updated and source of truth for both team and integrators)

[iamnivekx]

Wouldn’t it be better to keep the code aligned with the schema at https://dev.jup.ag/docs/api/swap-api? That helps avoid any mismatch between docs and implementation. That’s what I aimed for with this PR.