docs: remove deprecated CLI from lolor docs

[AntTheLimey]

What

The pgEdge CLI is deprecated, but the lolor docs still instruct users
to install with ./pgedge um install and to add tables to a
replication set with ./pgedge spock repset-add-table. This rewrites
those instructions to be deployment-aware and SQL-based.

docs/install_configure.md

• Replaces ./pgedge um install lolor with a platform/source install:
  lolor ships with pgEdge Distributed/Enterprise Postgres (the Control
  Plane installs the package per node), or build from source with PGXS.
• Removes the leftover "um module" reference in the CREATE EXTENSION
  lead-in.
• Replaces the two ./pgedge spock repset-add-table commands with
  SELECT spock.repset_add_table(...) run in the lolor database.

README.md

• Applies the same spock.repset_add_table() SQL replacement for the
  replication-set instructions.

Verification

• spock.repset_add_table('set', 'schema.table') signature confirmed
  against Spock's regression suite.
• Control Plane packaging of lolor confirmed in control-plane.
• No residual ./pgedge / CLI references remain in the docs.

Targets main; picked up by the next tagged lolor release.

Note: the Configuring section's lolor.node range ("1 to 2^28") looks
incorrect - the source caps it at 16 - but that is unrelated to the CLI
cleanup and is left untouched here.

[coderabbitai]

Warning

Review limit reached

@AntTheLimey, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 58 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 427a46fd-69f4-418e-b3d5-fcab5a6c1c0d

📥 Commits

Reviewing files that changed from the base of the PR and between e4949b4 and 84c225d.

📒 Files selected for processing (2)

• README.md
• docs/install_configure.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/remove-deprecated-cli

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}