docs: add proprietary CLI installation flow and update installation page

[kirti763]

What has changed?

• Adds the new Recommended: Keploy Proprietary CLI installation section
• Keeps OSS installation as secondary option
• Adds feature comparison table (OSS vs Enterprise)
• Updates installation page structure based on team discussion

Please include a summary of the change.

This PR Resolves #(issue)

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue).
• New feature (non-breaking change which adds functionality).
• Breaking change (fix or feature that would cause existing functionality to not work as expected).
• Documentation update (if none of the other choices apply).

How Has This Been Tested?

Please run npm run build and npm run serve to check if the changes are working as expected. Please include screenshots of the output of both the commands. Add screenshots/gif of the changes if possible.

Checklist:

• My code follows the style guidelines of this project.
• I have performed a self-review of my own code.

[PrathamSikka24]

Changes suggested:

1. Update the text in the first section "Install Keploy" to match the content in the shared reference Google Doc.

2. It should have an Enterprise label on top also, and that should be before the green OSS label on top.

3. In Choose your setup path,
   replace
   Recommended: Keploy Proprietary CLI
   with
   Recommended: Keploy Enterprise CLI

4. In the "Choose your setup path" section, i have put a highlighter box reference in the google doc. Please put these two lines in the blue highlighter box:
   "
   Recommended: Keploy Enterprise CLI
   Use this if you want the fastest setup, browser-based sign-in, and access to Keploy’s Enterprise capabilities.
   "
   it is also mentioned in the doc.

5. The " Recommended Setup: Keploy Proprietary CLI " section is now replaced and a comment is added in the google doc regarding the dropdown, and internal text to be gated behind the dropdown.

6. This command: keploy record -c "YOUR_START_COMMAND"

should also come like a code snippet, in the same way like you have written the next command keploy test -c "YOUR_START_COMMAND" --delay 10

The record command should also come like a code snippet and be a copyable element because we want people to copy it.

[PrathamSikka24]

1. In the "Why this is the recommended path " add a question mark to this subheading.
   Replace " Use the recommended Keploy CLI if you want: " with " Use the recommended Keploy Enterprise CLI if you want: "

Please make sure it is in sync with the updated Google Doc.

2. The feature comparison table in the "Which path should I choose?" section is not fully and correctly rendered. The last few rows are outside of the table. Additionally, the table should span the full width, occupying more space on the page and being well-indented. It should have a width similar to that of the info highlight blue box.

3. Replace " Setup: Open-source only " ---> with " Setup: Open-source "

[PrathamSikka24]

• Please remove the unnecessary space before the Automatic Cloud / Sandbox Behavior section.
• In the table, the Dependencies, the Incoming Tests, and the Extra Features should occupy the complete width in the table, and there should be no dividing lines, because those are parameters, so there should not be line dividing these options b/w open source and enterprise.
• In the table, the heading "Enterprise" should be centre aligned.
• Replace "Why this is the recommended path?" --> " Why is this the recommended path?" and inside the dropdown also. And change the heading of the dropdown from "Details" to "Know More".

[PrathamSikka24]

LGTM

[amaan-bhati]

LGTM!

[amaan-bhati]

For future refernce and a small potential improvement we can make in some other pr maybe:

• we can give the comparison table the full width instead of making it have a smaller width. Full width would create a better ui and ux.

@PrathamSikka24 @kirti763