Adds clarification for final page activation

[BoDonkey]

Summary

Summarize the changes briefly, including which issue/ticket this resolves. If it closes an existing Github issue, include "Closes #[issue number]" Adds clarification to the piece-pages documentation based on a Dev problem raised in the GitHub discussions. Closes PRO-4288.

What are the specific steps to test this change?

For example:

1. Run the website and log in as an admin
2. Open a piece manager modal and select several pieces
3. Click the "Archive" button on the top left of the manager and confirm that it should proceed
4. Check that all pieces have been archived properly
5. Build the documentation
6. Navigate to /guide/piece-pages.html

What kind of change does this PR introduce?

(Check at least one)

• [ ] Bug fix
• [ ] New feature
• [ ] Refactor
• [X] Documentation
• [ ] Build-related changes
• [ ] Other

Make sure the PR fulfills these requirements:

• [X] It includes a) the existing issue ID being resolved, b) a convincing reason for adding this feature, or c) a clear description of the bug it resolves
• [ ] The changelog is updated
• [ ] Related documentation has been updated
• [ ] Related tests have been updated

If adding a new feature without an already open issue, it's best to open a feature request issue first and wait for approval before working on it.

Other information:

[linear[bot]]

PRO-4288 Clarify addition of piece pages

Based on a Discussion in GitHub ([https://github.com/apostrophecms/apostrophe/discussions/4176](https://github.com/apostrophecms/apostrophe/discussions/4176)) some clarification is needed in the piece-page type documentation to make sure the dev adds the new page(s) to the `modules/apostrophecms/page/index.js` file.