Fix EDITORCONFIG violations: Add final newlines to all source files

- Add missing final newlines to 22+ files (.md, .py, .yaml)
- This resolves EDITORCONFIG linting errors in Super-Linter CI
- Files now conform to insert_final_newline = true rule

Author: vinod0m

CONTRIBUTING.md

@@ -155,4 +155,4 @@ Thank you in advance for your contribution!
 - [How to Contribute to Open Source](https://opensource.guide/how-to-contribute/)
 - [How to get faster PR reviews](https://github.com/kubernetes/community/blob/master/contributors/guide/pull-requests.md#best-practices-for-faster-reviews) by Kubernetes (but skip step 0)
 - [Using Pull Requests](https://help.github.com/articles/about-pull-requests/)
-- [GitHub Help](https://help.github.com)
+- [GitHub Help](https://help.github.com)

config/README.md

@@ -14,4 +14,4 @@ This folder contains the various configurations for unstructuredDataHandler espe
 
 - `model_config.yaml`: Configure API keys and model parameters
 - `prompt_templates.yaml`: Define reusable prompt templates
-- `logging_config.yaml`: Configure logging behavior
+- `logging_config.yaml`: Configure logging behavior

data/README.md

@@ -9,4 +9,4 @@ This folder contains the various data files for unstructuredDataHandler, includi
    ├── prompts/           # Prompt storage
    ├── outputs/           # Output storage
    └── embeddings/        # Embedding storage
-```
+```

doc/COOKED_READ_DATA.md

@@ -7,4 +7,4 @@ All of the following ✅ marks must be fulfilled during manual testing:
 * usecase 2 ✅
 * usecase 3 ✅
 * usecase 4 ✅
-* usecase 5 ✅
+* usecase 5 ✅

doc/CodeDocs/conf.py

@@ -60,4 +60,4 @@
 
 # Type hints configuration
 typehints_fully_qualified = False
-always_document_param_types = True
+always_document_param_types = True

doc/STYLE.md

@@ -3,4 +3,4 @@
 ## Philosophy
 1. If it's inserting something into the existing classes/functions, try to follow the existing style as closely as possible.
 1. If it's brand new code or refactoring a complete class or area of the code, please follow as Modern C++ of a style as you can and reference the [C++ Core Guidelines](https://github.com/isocpp/CppCoreGuidelines) as much as you possibly can.
-1. The use of NTSTATUS as a result code is discouraged, HRESULT or exceptions are preferred. Functions should not return a status code if they would always return a successful status code. Any function that returns a status code should be marked `noexcept` and have the `nodiscard` attribute.
+1. The use of NTSTATUS as a result code is discouraged, HRESULT or exceptions are preferred. Functions should not return a status code if they would always return a successful status code. Any function that returns a status code should be marked `noexcept` and have the `nodiscard` attribute.

doc/fuzzing.md

@@ -57,4 +57,4 @@ Our pipeline has been set up to create Azure DevOps work items.
 - [Notifications](https://github.com/microsoft/onefuzz/blob/main/docs/notifications.md)
     - [MS Teams](https://github.com/microsoft/onefuzz/blob/main/docs/notifications/teams.md)
     - [Azure DevOps](https://github.com/microsoft/onefuzz/blob/main/docs/notifications/ado.md)
-- [OSG Wiki - OneFuzz](https://www.osgwiki.com/wiki/Fuzzing_Service_-_Azure_Edge_and_Platform)
+- [OSG Wiki - OneFuzz](https://www.osgwiki.com/wiki/Fuzzing_Service_-_Azure_Edge_and_Platform)

examples/README.md

@@ -8,4 +8,4 @@ This folder contains the various examples for unstructuredDataHandler.
    ├── basic_completion.py
    ├── chat_session.py
    └── chain_prompts.py
-```
+```

examples/parser_demo.py

@@ -182,4 +182,4 @@ def main():
 
 
 if __name__ == "__main__":
-    main()
+    main()

notebooks/README.md

@@ -11,4 +11,4 @@ This folder contains the various notebooks for unstructuredDataHandler that used
     ├── response_analysis.ipynb
     └── model_experimentation.ipynb
 
-```
+```