Clarify code snippet use

[conceptualshark]

Description

Closes https://github.com/camunda/developer-experience/issues/284

Specifically, I'm trying to make sure each instance of configuration in the backup and restore docs appropriately describes how the user could actually make that config change/what file that change should occur in.

When should this change go live?

• This is a bug fix, security concern, or something that needs urgent release support.
• This is already available but undocumented and should be released within a week.
• This on a specific schedule and the assignee will coordinate a release with the DevEx team. (apply hold label or convert to draft PR)
• This is part of a scheduled alpha or minor. (apply alpha or minor label)
• There is no urgency with this change and can be released at any time.

PR Checklist

• My changes are for an already released minor and are in /versioned_docs directory.
• My changes are for the next minor and are in /docs directory (aka /next/).

• My changes require an Engineering review, and I've assigned the Engineering DRI or delegate.
• My changes require a technical writer review, and I've assigned @camunda/tech-writers as a reviewer.

[github-actions]

👋 🤖 ✅ Looks like the changes were ported across versions, nice job! 🎉

You can read more about the versioning within our docs in our documentation guidelines.

[christinaausley]

Hi @conceptualshark 👋 Are you still making changes here, or should this issue be moved to Ready, or are you ready for review?

[conceptualshark]

Sorry for the wait on this one, it should be ready to go!

[github-actions]

The preview environment relating to the commit 832a22f has successfully been deployed. You can access it at https://preview.docs.camunda.cloud/pr-4288/index.html