split into constants,v2,v3

[mkflow27]

This pr closes https://github.com/orgs/balancer/projects/9/?pane=issue&itemId=94402497&issue=balancer%7Cb-sdk%7C563 The constants were moved either to new file (v2, or v3) or left in the old one

[brunoguerios]

I like the idea of splitting the constants into 2 files so they are more organized, but if possible I'd like for constants themselves to also be differentiated with V2/V3 in their names.
I mean, reading the code is much easier to spot something like VAULT_V2 and VAULT_V3 than simply VAULT and having to look at the import to see it was imported from constantsV2 or constantsV3 file.
What do you think?

[mkflow27]

I like the idea of splitting the constants into 2 files so they are more organized, but if possible I'd like for constants themselves to also be differentiated with V2/V3 in their names.
I mean, reading the code is much easier to spot something like VAULT_V2 and VAULT_V3 than simply VAULT and having to look at the import to see it was imported from constantsV2 or constantsV3 file.
What do you think?

I think it is a good suggestion which will make the code more readable. I will implement it.
Edit: After looking through the code again, the only variable with a unclear naming would be vault -> Vault_v2. All other names can be tied to either general, v2 or v2 based on their name.