Summary of Changes

Hello @PeterSuna, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses a potential issue where the restconfServletContextPath configuration property, if containing a leading slash, could lead to incorrect behavior in object comparison methods. The change centralizes the logic for sanitizing this path by moving it into the ConfigUtils classes, where it is applied during JSON deserialization. This ensures that the internal representation of the path is consistently stored without a leading slash, thereby enhancing the robustness and predictability of configuration handling across the application.

Highlights

• Centralized Path Sanitization: The logic for removing leading slashes from the restconfServletContextPath has been moved from getter methods in configuration classes to dedicated utility methods within the ConfigUtils classes.
• Improved Configuration Consistency: Sanitization of the restconfServletContextPath now occurs during JSON deserialization, ensuring that the internal field always stores the path without a leading slash. This prevents potential inconsistencies that could affect equals() and hashCode() methods.
• Refactored Getters: The getRestconfServletContextPath() methods in RestConfConfiguration and NettyRestConfConfiguration have been simplified to directly return the stored path, as the sanitization is now handled earlier in the configuration loading process.
• New Utility Method: A private static removeSlashFromContextPath utility method has been introduced in both RestConfConfigUtils and NettyRestConfUtils to perform the leading slash removal on the JSON node during configuration parsing.