Remove Unused Projects

[kharithomas]

This PR aims to streamline the Ginger solution by eliminating dead code and obsolete legacy projects. The following projects have been identified for removal:

• GingerConsoleTest
• GingerWPFDriverWindow
• GingerWPFDriverWindowTest
• GingerWin64OsSupport

Upon careful review, the GingerConsoleTest project was found to lack actual test logic, serving only as a setup and teardown utility for several classes. Similarly, the GingerWin64OsSupport and GingerWPFDriverWindow projects are legacy components that are no longer referenced in the current codebase.

Removing these projects will reduce clutter and enhance clarity for new developers, fostering better understanding of the solution's structure.

==========================================

Thank you for your contribution.
Before submitting this PR, please make sure:

• PR description and commit message should describe the changes done in this PR
• Verify the PR is pointing to correct branch i.e. Release or Beta branch if the code fix is for specific release , else point it to master
• Latest Code from master or specific release branch is merged to your branch
• No unwanted\commented\junk code is included
• No new warning upon build solution
• Code Summary\Comments are added to my code which explains what my code is doing
• Existing unit test cases are passed
• New Unit tests are added for your development
• Sanity Tests are successfully executed for New and Existing Functionality
• Verify that changes are compatible with all relevant browsers and platforms.
• After creating pull request there should not be any conflicts
• Resolve all Codacy comments
• Builds and checks are passed before PR is sent for review
• Resolve code review comments
• Update the Help Library document to match any feature changes

[coderabbitai]

Walkthrough

The pull request involves the removal of two projects, GingerConsoleTest and GingerWin64OsSupport, from the Ginger solution. This change is reflected in both the Ginger.sln solution file and the Ginger.csproj project file. The solution file has had the project entries and configurations deleted, while the project file has removed project references, compile entries, resources, and other associated items related to these projects. Additionally, several XAML and code-behind files associated with user interface elements for managing application agents and runner controls have also been deleted.

Changes

File	Change Summary
Ginger/Ginger.sln	Removed project entries for GingerConsoleTest and GingerWin64OsSupport, including their project identifiers and paths.
Ginger/Ginger/Ginger.csproj	Deleted project reference to GingerWin64OsSupport.csproj, removed multiple Compile, EmbeddedResource, None, and Page entries.
Ginger/Ginger/Agents/AgentsNew/MapApplicationAgentPage.xaml	Removed the entire XAML file defining the UI for managing application agents.
Ginger/Ginger/Agents/AgentsNew/MapApplicationAgentPage.xaml.cs	Removed the code-behind file implementing the logic for MapApplicationAgentPage.
Ginger/Ginger/RunLibNew/GingerRunnerControlsPage.xaml	Removed the entire XAML file defining the UI for the Ginger runner controls.
Ginger/Ginger/RunLibNew/GingerRunnerControlsPage.xaml.cs	Removed the code-behind file implementing the logic for GingerRunnerControlsPage.

Possibly related PRs

• Ginger ATS Removed #3963: Similar project removal from Ginger.sln solution file.
• fix vrt artifact issue #3965: Modifications to project references and dependencies, indicating a cleanup effort.
• Feature - Import katalon object repository #3971: Introduces new files and modifications related to Katalon object repositories, potentially affecting project structure.
• Handled VRT version mismatch issue #3989: Addresses issues related to entity equality, which may connect to structural changes in the main PR.
• FIxed issue with Entity Equality #4025: Focuses on fixing issues with entity equality, relating to the overall cleanup and restructuring efforts.

Poem

🐰 Farewell, old projects, time to part,
Code cleanup with a rabbit's art!
Removing lines with gentle care,
Streamlining solution, beyond compare.
A leaner codebase, light and bright, 🔍
Hopping forward, into the night!

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 896d576 and b74647c.

📒 Files selected for processing (5)

• Ginger/Ginger.sln (0 hunks)
• Ginger/Ginger/Agents/AgentsNew/MapApplicationAgentPage.xaml (0 hunks)
• Ginger/Ginger/Agents/AgentsNew/MapApplicationAgentPage.xaml.cs (0 hunks)
• Ginger/Ginger/RunLibNew/GingerRunnerControlsPage.xaml (0 hunks)
• Ginger/Ginger/RunLibNew/GingerRunnerControlsPage.xaml.cs (0 hunks)

💤 Files with no reviewable changes (5)

• Ginger/Ginger.sln
• Ginger/Ginger/Agents/AgentsNew/MapApplicationAgentPage.xaml
• Ginger/Ginger/RunLibNew/GingerRunnerControlsPage.xaml.cs
• Ginger/Ginger/RunLibNew/GingerRunnerControlsPage.xaml
• Ginger/Ginger/Agents/AgentsNew/MapApplicationAgentPage.xaml.cs

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai or @coderabbitai title anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.