Add oe_builtin app note

[kprosise]

Added to an existing admonition, and changed admonition type from "note" to "important".

QA: Checked rendered output, no issues found.

This commit addresses FFTK-1660, "…OE Apps must be validated…"

PR Template and Checklist

Please complete as much as possible to speed up the reviewing process.

Readiness and adding reviewers as appropriate is required.

All PRs should be reviewed by a technical writer/documentation team and a peer.
If effecting customers—which is a majority of content changes—a member of Customer Success must also review.

Readiness

• Merge (pending reviews)
• Merge after date or event
• Draft

Overview

Older issue, but appears to still be applicable.

Checklist

• Run spelling and grammar check, preferably with linter.
• Avoid changing any header associated with a link/reference.
• Step through instructions (or ask someone to do so).
• Review for wordiness
• Match tone and style of page/section.
• Run make linkcheck.
• View HTML in a browser to check rendering.
• Use semantic newlines.
• follow best practices for commits.
  • Descriptive title written in the imperative.
  • Include brief overview of QA steps taken.
  • Mention any related issues numbers.
  • End message with sign off/DCO line (-s, --signoff).
  • Sign commit with your gpg key (-S, --gpg-sign).
  • Squash commits if needed.
• Request PR review by a technical writer and at least one peer.

Comments

Kept message terse, and isn't something which would apply for most folks.

[vanmaegima]

@kprosise can you clarify what this means?

[kprosise]

I can try, though there isn't much more info recorded anywhere, but I will check with the Platform team.

[vanmaegima]

I mean, I didn't understand what this means exactly, maybe it means that the apps and platform need to be aligned and verified before enabling container preloading?

[mike-sul]

I think this use-case is meant by This option does not work with some advanced tagging cases, e.g. multiple container builds using the same platform.

The OE builtin app preloading fails in such the case because there is an ambiguity in terms of which of the tags' apps to choose. For example, in the example provided in the doc the dilemma is: should be the apps of the main branch preloaded or the foo branch of the containers.git repo?

[vanmaegima]

I understand that, but not sure what "The Apps must be validated and without conflict" means in this context. Maybe we just remove this line as it's causing confusion?

[mike-sul]

@kprosise
Probably we just remove that phrase or replace it with something what I wrote above "The OE builtin app preloading fails in such the case because there is an ambiguity in terms of which of the tags' apps to choose..."?