- Introduce `getResourceDocsObpV700` to handle resource docs retrieval for API version 7.0.0
- Add `getResourceDocsList` helper function for fetching version-specific resource docs
- Update `allRoutes` to include the new endpoint
- Modify imports to include necessary utilities and remove unused references
- Add `Http4sEndpoint` type alias and `http4sPartialFunction` in APIUtil for handling http4s routes
- Refactor Http4s700 to define routes as standalone functions (e.g., `root`, `getBanks`) within Implementations7_0_0 object
- Attach resource documentation to each route for better maintainability
- Create a unified `allRoutes` combining v7.0.0 route handlers
- Update imports and clean up unused references
- Rename MappedAbacRule class to AbacRule for cleaner naming convention
- Extract AbacRuleTrait as the base trait for ABAC rule contracts
- Update AbacRuleProvider to return AbacRuleTrait instead of concrete class
- Update all references in Boot.scala to use new AbacRule naming
- Update JSONFactory6.0.0.scala to accept AbacRuleTrait in factory methods
- Simplify object singleton naming from MappedAbacRule to AbacRule
- Improves code clarity by separating trait definition from implementation
- Bump Jetty version from 9.4.50.v20250814 to 9.4.58.v20250814
- Ensures latest security patches and bug fixes are included
- Maintains compatibility with existing HTTP4s and Lift configurations
- Update view ID field references from "id" to "view_id" in getAllSystemViews test
- Update view ID field references from "id" to "view_id" in getOneSystemView test
- Update view ID field references from "id" to "view_id" in getMultipleSystemViews test
- Align test assertions with actual API response schema for system views endpoint
- Update WebUiPropsTest to assert empty body as JNothing instead of "{}"
- Change response body assertion to use `shouldBe(JNothing)` for proper HTTP 204 handling
- Remove default "{}" placeholder in SendServerRequests when response body is empty
- Return empty string "" instead of "{}" to correctly represent No Content responses
- Add clarifying comment explaining that HTTP 204 should have empty body, not JSON object
- Align test expectations with proper REST semantics for 204 No Content status code
