fix: add missing properties to schema

[pottekkat]

Description

Adds missing properties to the schema so that it can be used for validating configuration files more accurately.

Also consolidates all the schemas to a single schema instead of having to validate with multiple schemas.

Checklist

• I have explained the need for this PR and the problem it solves
• I have explained the changes or the new features added to this PR
• I have added tests corresponding to this change
• I have updated the documentation to reflect this change
• I have verified that this change is backward compatible (If not, please discuss on the APISIX mailing list first)

[pottekkat]

I'm unsure why the tests are failing.

[Revolyssup]

@pottekkat Can you change this to string? The test will pass
https://github.com/apache/apisix/pull/10339/files#diff-33a40d0c58eba6fec065b7df0f75fd0637387555e3ad0170d8e6674948575093R573

Because you can see this is a string and not number.

apisix/t/cli/test_main.sh

Line 527 in 33ee8d6

client_max_body_size: 512m

[pottekkat]

@Revolyssup I got this error before so I tried changing it:

https://github.com/apache/apisix/actions/runs/6549717930/job/17787244082?pr=10339#step:5:287

But it should be string though.

[pottekkat]

@Revolyssup Should we add a case where it can be either a string or a number?

[monkeyDluffy6017]

LGTM, That's a pretty big change. So let's make the ci pass

[Revolyssup]

@pottekkat Will you make sure that this dependency schema fits right with this[1] yaml snippet here?

1. https://github.com/apache/apisix/blob/88406dceab26ed7f25b663088b0b5e760bd45a38/t/cli/test_validate_config.sh#L210C1-L210C1

[pottekkat]

I reverted to the same changes as in the last commit where the tests were passing in this commit: bf8bdb8

But now, the tests fail.

I'm now trying by removing all changes and checking if the tests pass now and build from there.

[pottekkat]

All checks pass with these changes.

[pottekkat]

It seems like the issue might have been in the etcd schema and with merging the config and deployment schemas. Checking what the issue is incrementally.

[monkeyDluffy6017]

@Revolyssup please help to check