Create test infrastructure for Monkey365

Add the base Pester test infrastructure under the existing tests directory. This should provide a common structure and configuration that can be reused as test coverage is added to Monkey365.

Initial structure:

tests/
├── QA/
├── authentication/
├── unit/
│   ├── core/
│   └── modules/
└── monkey365pester.config.ps1

To implement

• Add tests/monkey365pester.config.ps1 with the common Pester 6.x configuration.
• The test infrastructure should:
  • Write test results to a configurable output path.
  • Generate pester-monkey365-summary.json with pass/fail counts and test duration.
  • Generate pester-failures.json with the test name, file path, error message and stack trace for failed tests.
  • Support code coverage.
  • Return the proper exit code when tests fail.
  • Generate NUnit test results for CI.
• Work with GitHub Actions and Azure DevOps pipelines.
• Include shared helpers where needed to avoid duplicating test setup.

This will be the base for adding unit tests for core functionality, authentication and individual Monkey365 modules.

Related

• #188

Start in the existing tests directory and read the related issue #188 for context before creating tests/monkey365pester.config.ps1. Define the shared Pester configuration and helpers around the requested output, coverage, failure, NUnit, and exit-code requirements, then verify the structure works with both GitHub Actions and Azure DevOps pipelines.