Add Test Integration Connectivity endpoint to API documentation and i…

[dhirmadi]

…mplementation

This commit introduces a new endpoint for testing integration connectivity and token validity, including a one-time refresh retry mechanism for access tokens. The API documentation is updated to reflect this addition, detailing the endpoint, authentication requirements, response examples, and rate limiting. This enhancement improves the usability of the integration testing process for tenants and ensures better error handling and feedback during connectivity checks.

Pull Request

Description

Brief description of the changes in this PR.

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Refactoring (no functional changes)
• Performance improvement
• Test coverage improvement

Related Issues

Closes #(issue number)

Changes Made

• Change 1
• Change 2
• Change 3

Documentation Impact

• No documentation changes needed
• I have updated the Architecture Reference
• I have updated the API Documentation
• I have updated the Feature Documentation
• I have updated the Integration Guides
• I have updated the Frontend Documentation
• I have updated the Testing Documentation
• I have updated the README.md

Testing

• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• I have checked the Testing Documentation for guidance
• I have run npm run docs:validate to check documentation links

Security Considerations

• This change does not introduce security vulnerabilities
• I have reviewed the security implications
• Authentication/authorization is properly implemented
• Input validation is in place where needed

Architecture Compliance

• This change follows the patterns in Architecture Reference
• This change aligns with the Domain Map
• This change follows the Feature Patterns
• API changes follow the API Documentation standards

Checklist

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

Screenshots (if applicable)

Add screenshots to help explain your changes.

Additional Notes

Any additional information that reviewers should know.

[openhands-ai]

Looks like there are a few issues preventing this PR from being merged!

• GitHub Actions are failing:
  • Documentation Validation

If you'd like me to help, just leave a comment, like

@OpenHands please fix the failing actions on PR #68 at branch `token-test-endpoint`

Feel free to include any additional details that might help me get this PR into a better state.

_{^{You can manage your notification settings}}