chore: bump code-block for shell-sesh fix

[zchsh]

🔗 Relevant links

• Preview link 🔎
• Asana task 🎟️

🗒️ What

Bumps @hashicorp/react-code-block to pull in a fix for shell-session CodeTabs from hashicorp/react-components#768.

🤷 Why

Fixes a bug where shell-session snippets within CodeTabs would copy correctly via the Copy button, but would still include the $ character when selected and copied by clicking and dragging.

🧪 Testing

• Visit a page with shell-session snippets in MDX CodeTabs, such as /consul/tutorials/network-infrastructure-automation/consul-terraform-sync-intro
  • The Copy button should copy without the leading $ or leading space that follows it
  • Selecting and copying all the text (eg by triple-clicking) should copy without the leading $.
    • Note the leading space will be copied, this is a difficult thing to optimize, and we haven't yet had the bandwidth to scope out a more holistic and robust approach to authoring and rendering shell-session snippets with multiple commands.
    • The leading space shouldn't affect the functionality of the command.

💭 Anything else?

See hashicorp/react-components#768 for details, including screenshots etc.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated
dev-portal	✅ Ready (Inspect)	Visit Preview	Oct 20, 2022 at 2:32PM (UTC)

[github-actions]

Some suggested prefixes and emojis that may help to write clear, actionable code review comments:

Praise 🙌	Question 🙋	Thought 💭	Blocker 🚧	Future 📌	Optional 🎨	Nitpick ⛏️

Expand for comment prefix descriptions

Prefix+Emoji	Description
Praise 🙌	Use to highlight something positive. It's nice to try to leave one per review, but don't leave false praise just to leave one of these comments.
Question 🙋	Use to gain clarity from the code author. The conversation could evolve into any one of these other categories. Only the reviewer should resolve these comment threads.
Thought 💭	Use to share context, leave a breadcrumb, or share an idea that came up while reviewing.
Blocker 🚧	Use to request changes that block merging the current PR. Only the reviewer should resolve these comment threads.
Future 📌	Use to request changes that the code author can choose to address in the current PR or a follow-up one.
Optional 🎨	Use to suggest optional changes that you feel strongly about but ultimately defer to the code author to make a decision on. These can be comments that turn into valuable conversation starters for adopting new code styles, guidelines, or team practices.
Nitpick ⛏️	Use to suggest changes based on loose opinions or personal preferences. The difference between this and Optional 🎨  is how strong the code reviewer's opinion is.

[github-actions]

📦 Next.js Bundle Analysis

This analysis was generated by the next.js bundle analysis action 🤖

This PR introduced no changes to the javascript bundle 🙌

[zchsh]

🚧 Will bump to stable once hashicorp/react-components#768 lands 👍

[zchsh]

✅ released & bumped

[BRKalow]

Good detective work 🕵️