expands platform lifecycle tutorial (#769)

* expands platform lifecycle tutorial

Signed-off-by: Hanan Younes <[email protected]>

* adds detect section & updates few links

Signed-off-by: Hanan Younes <[email protected]>

* Fix recursive copy of samples

Make the recursive copy of samples work
correctly in the expected tutorial directory
structure.

Co-authored-by: Natalie Arellano <[email protected]>
Signed-off-by: Aidan Delaney <[email protected]>

---------

Signed-off-by: Hanan Younes <[email protected]>
Signed-off-by: Aidan Delaney <[email protected]>
Co-authored-by: Aidan Delaney <[email protected]>
Co-authored-by: Natalie Arellano <[email protected]>
Co-authored-by: Aidan Delaney <[email protected]>

docs/for-platform-operators/concepts/lifecycle/analyze/index.html

@@ -907,7 +907,7 @@ <h1 class="title">Analyze</h1>
 This information is used during the <code>export</code> phase in order to avoid re-uploading unchanged layers.<br>
 Starting from <code>Platform API 0.7</code>, the <code>analyze</code> phase runs before the <code>detect</code> phase in order to validate registry access for all images that are used during the <code>build</code> as early as possible. In this way it provides faster failures for end users. The other responsibilities of the <code>analyzer</code> were moved to the <code>restorer</code>.<br>
 For more information, please see <a href="https://buildpacks.io/docs/for-platform-operators/how-to/migrate/deprecated/platform-api-0.6-0.7/">this migration guide</a>.</p>
-<p>The <code>lifecycle</code> should attempt to locate a reference to the latest <code>OCI image</code> from a previous build that is readable and was created by the <code>lifecycle</code> using the same application source code. If no such reference is found, the <code>analysis</code> is skipped.\</p>
+<p>The <code>lifecycle</code> should attempt to locate a reference to the latest <code>OCI image</code> from a previous build that is readable and was created by the <code>lifecycle</code> using the same application source code. If no such reference is found, the <code>analysis</code> is skipped.</p>
 <p>The <code>lifecycle</code> must write <a href="https://github.com/buildpacks/spec/blob/main/platform.md#analyzedtoml-toml">analysis metadata</a> to <code>&lt;analyzed&gt;</code>, where:</p>
 <ul>
 <li><code>image</code> MUST describe the <code>&lt;previous-image&gt;</code>, if accessible</li>

docs/for-platform-operators/tutorials/index.html

@@ -906,7 +906,7 @@ <h1 class="title">Tutorials</h1>
 
 
           <h2><a href="https://buildpacks.io/docs/for-platform-operators/tutorials/lifecycle/" class="">Orchestrate a build with the CNB lifecycle</a></h2>
-          <p class="m-1">Coming soon! In the meantime check out this excellent <a href="https://medium.com/buildpacks/unpacking-cloud-native-buildpacks-ff51b5a767bf">blog post</a> from our community.</p>
+          <p class="m-1">A <code>platform</code> orchestrates builds by invoking the <a href="https://buildpacks.io/docs/for-platform-operators/concepts/lifecycle/">lifecycle</a> binary together with buildpacks and application source code to produce a runnable <code>OCI image</code>.</p>