docs: Add dev container repo to readme

[czentgr]

Description

Motivation and Context

Impact

Test Plan

Contributor checklist

• Please make sure your submission complies with our contributing guide, in particular code style and commit standards.
• PR description addresses the issue accurately and concisely. If the change is non-trivial, a GitHub Issue is referenced.
• Documented new properties (with its default value), SQL syntax, functions, or other functionality.
• If release notes are required, they follow the release notes guidelines.
• Adequate tests were added if applicable.
• CI passed.
• If adding new dependencies, verified they have an OpenSSF Scorecard score of 5.0 or higher (or obtained explicit TSC approval for lower scores).

Release Notes

Please follow release notes guidelines and fill in the release notes below.

== NO RELEASE NOTE ==

Summary by Sourcery

Document development container support and reference the dedicated presto-dev repository from the main README.

Enhancements:

• Clean up minor trailing whitespace in the main README.

Documentation:

• Add a README section describing how to use development containers via the separate presto-dev repository.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates the main README to clean up whitespace and add a short section pointing contributors to the separate presto-dev repository for development container support.

File-Level Changes

Change	Details	Files
Clean up trailing whitespace in existing README sections.	Remove trailing space after the Mission and Architecture link line. Remove extra double-space at the end of the Java 17 configuration sentence.	README.md
Document availability of development containers via the separate presto-dev repository.	Add a new "Using development containers" section near the end of the README. Explain that dev container support lives in a dedicated repository. Link to the presto-dev repository and its README for setup details.	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.

[sourcery-ai]

Hey - I've found 1 issue, and left some high level feedback:

• The new dev containers section ends without terminal punctuation; consider adding a period at the end of the last sentence for consistency with the rest of the README.
• In the dev containers section, you can simplify the wording and links by using a single link (e.g., Please visit the [presto-dev README](https://github.com/prestodb/presto-dev/blob/main/README.md) for details.) instead of separate presto-dev and README links.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- The new dev containers section ends without terminal punctuation; consider adding a period at the end of the last sentence for consistency with the rest of the README.
- In the dev containers section, you can simplify the wording and links by using a single link (e.g., `Please visit the [presto-dev README](https://github.com/prestodb/presto-dev/blob/main/README.md) for details.`) instead of separate `presto-dev` and `README` links.

## Individual Comments

### Comment 1
<location> `README.md:162` </location>
<code_context>

+## Using development containers
+
+The Prestodb project provides support for development containers in its own repository.
+Please visit the [presto-dev](https://github.com/prestodb/presto-dev) [README](https://github.com/prestodb/presto-dev/blob/main/README.md) for details

</code_context>

<issue_to_address>
**issue (typo):** Consider correcting the project name capitalization to "PrestoDB".

```suggestion
The PrestoDB project provides support for development containers in its own repository.
```
</issue_to_address>

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[steveburnett]

LGTM! (docs)

[pramodsatya]

Thanks @czentgr.

[steveburnett]

This PR is ready to merge, except for a failing test.