New lazer structure

[yorunoken]

This pull request updates the library to the api version after lazer's pp release.

[L-Mario564]

I see a lot of breaking changes here, I think it would be best to have the user be able to specify the x-api-version header specifically in the endpoints in which they can be applied and then map out the return types as needed.

[yorunoken]

I see a lot of breaking changes here, I think it would be best to have the user be able to specify the x-api-version header specifically in the endpoints in which they can be applied and then map out the return types as needed.

so, an enum you would pass in the Client class while initializing the client?

const client = new Client(accessToken, ApiVersion.Lazer);

enum name would be subject to change.

[yorunoken]

dude, I just accidently deleted the branch

[yorunoken]

I named the old types to have Legacy at the start, let me know if I should put anything else.

[yorunoken]

@L-Mario564

I see a lot of breaking changes here, I think it would be best to have the user be able to specify the x-api-version header specifically in the endpoints in which they can be applied and then map out the return types as needed.

I've adressed the breaking changes. It now automatically returns the old structure unless you pass in true after required parameters.