feat(robotcode): introduce support for .gitignore and .robotignore during test suite discovery

Implemented support for `.gitignore` and `.robotignore` files in the discovery process of Robot Framework test suites and test cases.

**Motivation**:
The existing exclusion mechanism in Robot Framework, which only ignores files starting with `.` or `_`, and `CSV` directories, is insufficient for modern projects. These projects often include large repositories with test data, build directories, virtual environments (e.g., Python venv), `node_modules`, and other generated files that should be excluded during test discovery. Thus, additional flexibility was needed to control which files and directories should be ignored.

**`.robotignore` file**:
Introduced a new `.robotignore` file specifically for Robot Framework discovery.
- The syntax of `.robotignore` mirrors that of `.gitignore`, making it familiar and easy to use.
- When a `.robotignore` file is present, it takes priority over any `.gitignore` files in the same directory or its subdirectories. This allows users to fine-tune which files or directories to exclude, independent of the rules defined in the `.gitignore`.
- `.robotignore` files are hierarchical: if a `.robotignore` file is found in a directory, the discovery process will continue searching for `.robotignore` files in its subdirectories. Any `.gitignore` files found in those subdirectories will be ignored if a `.robotignore` file is present.

**`.gitignore` support**:
In addition to `.robotignore`, the discovery process now respects `.gitignore` files when a `.robotignore` file is absent. This brings better alignment with existing practices, as many projects already maintain `.gitignore` files to filter out unnecessary files and directories (e.g., build artifacts, dependency directories, etc.).

**Priority rules**:
- If both `.robotignore` and `.gitignore` files are found in the same directory, `.robotignore` takes precedence.
- If only a `.gitignore` file is present, it will be respected during test suite discovery.

**VSCode/RobotCode compatibility**:
Improved integration with the VSCode extension `RobotCode`. Specifically, users leveraging the `robotcode.workspace.excludePatterns` setting will benefit from optimized pattern matching:
- Files and directories are now ignored globally without the need for leading `**`, similar to `.gitignore` behavior.

**Benefits**:
- Provides more granular control over the test discovery process by allowing specific exclusions that are tailored to testing needs, rather than being tied to version control ignore rules.
- Helps improve performance and accuracy when running tests by preventing unnecessary files or directories from being included in the discovery process.
- Reduces potential conflicts between version control and test discovery exclusion needs, allowing each to be managed independently where necessary.

**Usage scenarios**:
- Large projects with complex directory structures can now use `.robotignore` to exclude directories like `venv`, `build`, `dist`, `node_modules`, etc., that would otherwise slow down the test discovery process.
- Teams can use `.robotignore` files to establish testing-specific exclusions without affecting the rules for version control maintained in `.gitignore`.

**Backward compatibility**:
The existing behavior of ignoring files that begin with `.` or `_` and `CSV` directories remains intact. The new `.robotignore` and `.gitignore` handling is additive, enhancing the flexibility without breaking current projects.

closes  #286

Author: d-biehl

.robotignore

@@ -0,0 +1,301 @@
+# Byte-compiled / optimized / DLL files
+__pycache__/
+*.py[cod]
+*$py.class
+
+# C extensions
+*.so
+
+# Distribution / packaging
+.Python
+build/
+develop-eggs/
+dist/
+downloads/
+eggs/
+.eggs/
+lib/
+lib64/
+sdist/
+var/
+wheels/
+share/python-wheels/
+*.egg-info/
+.installed.cfg
+*.egg
+MANIFEST
+
+# PyInstaller
+#  Usually these files are written by a python script from a template
+#  before PyInstaller builds the exe, so as to inject date/other infos into it.
+*.manifest
+*.spec
+
+# Installer logs
+pip-log.txt
+pip-delete-this-directory.txt
+
+# Unit test / coverage reports
+htmlcov/
+.tox/
+.nox/
+.coverage
+.coverage.*
+.cache
+nosetests.xml
+coverage.xml
+*.cover
+*.py,cover
+.hypothesis/
+.pytest_cache/
+cover/
+
+# profiler
+prof/
+
+# Translations
+*.mo
+*.pot
+
+# Django stuff:
+*.log
+local_settings.py
+db.sqlite3
+db.sqlite3-journal
+
+# Flask stuff:
+instance/
+.webassets-cache
+
+# Scrapy stuff:
+.scrapy
+
+# Sphinx documentation
+docs/_build/
+
+# PyBuilder
+.pybuilder/
+target/
+
+# Jupyter Notebook
+.ipynb_checkpoints
+
+# IPython
+profile_default/
+ipython_config.py
+
+# pyenv
+#   For a library or package, you might want to ignore these files since the code is
+#   intended to run in multiple environments; otherwise, check them in:
+# .python-version
+
+# pipenv
+#   According to pypa/pipenv#598, it is recommended to include Pipfile.lock in version control.
+#   However, in case of collaboration, if having platform-specific dependencies or dependencies
+#   having no cross-platform support, pipenv may install dependencies that don't work, or not
+#   install all needed dependencies.
+#Pipfile.lock
+
+# PEP 582; used by e.g. github.com/David-OConnor/pyflow
+__pypackages__/
+
+# Celery stuff
+celerybeat-schedule
+celerybeat.pid
+
+# SageMath parsed files
+*.sage.py
+
+# Environments
+.env
+.venv
+env/
+venv/
+ENV/
+env.bak/
+venv.bak/
+.hatch/
+
+# Spyder project settings
+.spyderproject
+.spyproject
+
+# Rope project settings
+.ropeproject
+
+# mkdocs documentation
+/site
+
+# mypy
+.mypy_cache/
+.dmypy.json
+dmypy.json
+
+# Pyre type checker
+.pyre/
+
+# pytype static type analyzer
+.pytype/
+
+# Cython debug symbols
+cython_debug/
+
+.vscode/*
+#!.vscode/settings.json
+!.vscode/tasks.json
+!.vscode/launch.json
+!.vscode/extensions.json
+*.code-workspace
+
+# Local History for Visual Studio Code
+.history/
+
+# Logs
+logs
+*.log
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+lerna-debug.log*
+
+# Diagnostic reports (https://nodejs.org/api/report.html)
+report.[0-9]*.[0-9]*.[0-9]*.[0-9]*.json
+
+# Runtime data
+pids
+*.pid
+*.seed
+*.pid.lock
+
+# Directory for instrumented libs generated by jscoverage/JSCover
+lib-cov
+
+# Coverage directory used by tools like istanbul
+coverage
+*.lcov
+
+# nyc test coverage
+.nyc_output
+
+# Grunt intermediate storage (https://gruntjs.com/creating-plugins#storing-task-files)
+.grunt
+
+# Bower dependency directory (https://bower.io/)
+bower_components
+
+# node-waf configuration
+.lock-wscript
+
+# Compiled binary addons (https://nodejs.org/api/addons.html)
+build/Release
+
+# Dependency directories
+node_modules/
+jspm_packages/
+
+# Snowpack dependency directory (https://snowpack.dev/)
+web_modules/
+
+# TypeScript cache
+*.tsbuildinfo
+
+# Optional npm cache directory
+.npm
+
+# Optional eslint cache
+.eslintcache
+
+# Microbundle cache
+.rpt2_cache/
+.rts2_cache_cjs/
+.rts2_cache_es/
+.rts2_cache_umd/
+
+# Optional REPL history
+.node_repl_history
+
+# Output of 'npm pack'
+*.tgz
+
+# Yarn Integrity file
+.yarn-integrity
+
+# dotenv environment variables file
+.env
+.env.test
+
+# parcel-bundler cache (https://parceljs.org/)
+.cache
+.parcel-cache
+
+# Next.js build output
+.next
+out
+
+# Nuxt.js build / generate output
+.nuxt
+dist
+
+# Gatsby files
+.cache/
+# Comment in the public line in if your project uses Gatsby and not Next.js
+# https://nextjs.org/blog/next-9-1#public-directory-support
+# public
+
+# vuepress build output
+.vuepress/dist
+
+# Serverless directories
+.serverless/
+
+# FuseBox cache
+.fusebox/
+
+# DynamoDB Local files
+.dynamodb/
+
+# TernJS port file
+.tern-port
+
+# Stores VSCode versions used for testing VSCode extensions
+.vscode-test
+
+vscode.d.ts
+vscode.proposed.d.ts
+
+# yarn v2
+.yarn/cache
+.yarn/unplugged
+.yarn/build-state.yml
+.yarn/install-state.gz
+.pnp.*
+
+*.vsix
+
+# playground files
+playground/
+
+# pycharm
+.idea/
+
+# test results
+test-results
+results.html
+report.html
+
+# pyenv
+.python-version
+
+# robotcode
+.robotcode_cache/
+
+# ruff
+.ruff_cache/
+
+bundled/libs
+
+# robotframework
+results/
+
+# data
+_regtest_outputs/

.vscode/launch.json

@@ -47,7 +47,7 @@
 				// "analyze",
 
 				"discover",
-				"tests",
+				"suites",
 				// "discover", "tests", "--tags"
 				"."
 			]

package.json

@@ -832,14 +832,13 @@
           "robotcode.workspace.excludePatterns": {
             "type": "array",
             "default": [
-              "**/.git/",
-              "**/.hatch/",
-              "**/.venv/",
-              "**/node_modules/",
-              "**/.pytest_cache/",
-              "**/__pycache__/",
-              "**/.mypy_cache/",
-              "**/.robotcode_cache/"
+              ".hatch/",
+              ".venv/",
+              "node_modules/",
+              ".pytest_cache/",
+              "__pycache__/",
+              ".mypy_cache/",
+              ".robotcode_cache/"
             ],
             "items": {
               "type": "string"