admin_pages_dev: Modified ReadMe file

[Riyad-Murad]

Summary by Sourcery

Revise README file to reorganise demo tables, update screenshots, rename headings and labels, and add indexing and logging examples.

Documentation:

• Simplify "Provider Screens" heading by removing the "(Web)" suffix.
• Clean up GitHub testing section by dropping the output column and updating the pipeline screenshot to production.
• Reorganise AI demo section into separate tables for provider/client prompts, function calls with controller, and routes/testing pipeline.
• Update response time labels to "AI generated response time difference" and include indexing screenshots for users and metrics tables.
• Revamp deployment section with multiple two-column pipeline tables, add Node server logs and ESP32 serial monitor images.
• Standardise S3 deployment image alt texts and labels.

[sourcery-ai]

Reviewer's Guide

This PR restructures README.md by updating section headings, simplifying and expanding example tables, renaming entries, and adding new demonstration images for testing, AI demos, response-time indexing, and deployment processes.

File-Level Changes

Change	Details	Files
Updated section headings	Renamed “Provider Screens (Web)” to “Provider Screens” Adjusted section titles for clarity and consistency	README.md
Reformatted GitHub testing table	Removed the third “Testing Output” column Swapped in production pipeline image for testing Simplified table layout to two columns	README.md
Reorganized AI demo tables	Reordered prompt images (Provider before Client) Separated Prism Function Call and Controller visuals into their own table Added a new table for Routes and Testing Pipeline screenshots	README.md
Refined response-time labels and added indexing visuals	Updated “response time difference” labels to include “AI generated” Introduced images for user_type and slave_id indexing results	README.md
Expanded deployment section visuals	Split deployment pipeline images into four distinct tables Added tables for EC2 logs and ESP32 serial monitor output Renamed S3 section images for React and public link	README.md

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.