fix path handling on windows and add contribution section in README.md

[emmanuel39hanks]

Type of change

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update

Description

The main fix addresses the Windows path validation issue where the scan endpoint was failing with "Invalid file path" errors. The validation logic has been updated to handle both backslash and forward slash formats, ensuring support for both Windows and Unix-style paths. Additionally, improvements were made to support absolute and relative path resolution.

Documentation updates include:

• Detailed contribution guide with platform-specific examples.
• Instructions for running the project on Windows and Unix platforms.
• Example paths and workflows for development.

These changes improve platform compatibility and enhance developer guidance.

Related Issue

Issue Number: #42

Motivation and Context

This change was required to address path handling issues on Windows that caused errors when using the scan endpoint. Proper validation and documentation improvements ensure a consistent development and user experience across all platforms.

How Has This Been Tested?

The changes were tested by:

• Verifying path validation with both absolute and relative paths on Windows and Unix systems.
• Testing the scan endpoint to ensure it handles Windows-style paths correctly.

Screenshots (if appropriate):

Checklist

• I have read the contributing guidelines
• My code follows the code style of this project.
• I have added tests that prove my fix is effective or that my feature works
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• Any dependent changes have been merged and published