(docs) Staying up to date, troublshooting

[ZacButko]

Requirements

• This PR has a title that briefly describes the work done, including the ticket number if there is a ticket.

For changes to apps

• [n/a] My work conforms to the OpenMRS 3.0 Styleguide.

If applicable

• [n/a] My work includes tests or is validated by existing tests.
• [n/a] I have updated the esm-framework mock to reflect any API changes I have made.

Summary

Adds docs which enumerate troubleshooting steps regarding keeping a local codebase up to date and how to clear browser cache

Screenshots

n/a

Related Issue

n/a

Other

I'm not a terribly big fan of the format or placement of these troubleshooting tips. If anyone has suggestions how to improve delivery or placement I'm all ears

[github-actions]

---

Error: Error while trying to collect info after merging docs/clearing-cache into master.

Error: git merge command failed (is there a merge conflict?)
    at commentPrImpact (file:///home/runner/work/openmrs-esm-core/openmrs-esm-core/node_modules/@jsenv/github-pull-request-impact/src/commentGitHubPullRequestImpact.js:314:13)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async commentGitHubPullRequestImpact (file:///home/runner/work/openmrs-esm-core/openmrs-esm-core/node_modules/@jsenv/github-pull-request-impact/src/commentGitHubPullRequestImpact.js:82:12)
    at async file:///home/runner/work/openmrs-esm-core/openmrs-esm-core/tools/size-reporter.mjs:6:1

---

_{Generated by @jsenv/file-size-impact during Report bundle size#2784924671 on 28a916d}

[ibacher]

It might be best just to create a new page for this?

[brandones]

Thanks Zac! I kind of feel like this should be merged with the FAQ? It's very FAQ-like.

[ibacher]

@ZacButko In addition to @brandones comments, could you retarget this to point at main instead of master?

[ZacButko]

@ibacher changes made.