feat: Support for token based authentication and addition of helpers for organisation apis

[AsabuHere]

Fixes

A short description of what this PR does.

The Page class in bearertoken section is responsible for handling the pagination. This fetch "meta" information from the root level and use this information for pagination. For /scim/Users endpoint, this information is not present at root level which is causing the sdk to break. To avoid this added a null check after fetching "meta" from root level and proceed only if its not null

Checklist

• [x] I acknowledge that all my contributions will be made under the project's license
• [x] I have made a material change to the repo (functionality, testing, spelling, grammar)
• [ ] I have read the Contribution Guidelines and my PR follows them
• [x] I have titled the PR appropriately
• [ ] I have updated my branch with the main branch
• [ ] I have added tests that prove my fix is effective or that my feature works
• [x] I have added the necessary documentation about the functionality in the appropriate .md file
• [x] I have added inline documentation to the code I modified

If you have questions, please file a support ticket, or create a GitHub Issue in this repository.

[sbansla]

@AsabuHere Going forward all APIs will be moving towards Bearer Token Authentication, So we don't want to change pagination just for one API. [Important] Make sure whatever pagination you are using for Orgs API is compatible with other APIs as well. Add summary to PR.

Rest Proxy supports 2 types of pagination. I will message you what are those pagination and we don't want to support any 3rd pagination technique.

[AsabuHere]

@AsabuHere Going forward all APIs will be moving towards Bearer Token Authentication, So we don't want to change pagination just for one API. [Important] Make sure whatever pagination you are using for Orgs API is compatible with other APIs as well. Add summary to PR.

Rest Proxy supports 2 types of pagination. I will message you what are those pagination and we don't want to support any 3rd pagination technique.

This is not addition of a new pagination mechanism. This is just handling of a null pointer issue. When meta is not present, the sdk is breaking, to prevent that added a check to verify if meta is null or not before actually using it

@sbansla @kridai Can you please approve?

[kridai]

@AsabuHere We also need an example of how the auth token based authentication apis will be called via the client /customer. Could you please add an example here

[AsabuHere]

@AsabuHere We also need an example of how the auth token based authentication apis will be called via the client /customer. Could you please add an example here

Added

[AsabuHere]

@AsabuHere We also need an example of how the auth token based authentication apis will be called via the client /customer. Could you please add an example here

added