editorial: Relying Party Endpoints Section and terms

[peppelinux]

This PR aims to resolve #862 using an hierarchical structure with proper terminology, no content duplication, and EN/IT alignment.

the PR has:

1. Renamed relying-party-endpoints.rst → relying-party-remote-flow-endpoints.rst
2. Created new parent relying-party-endpoints.rst with introduction and includes
3. Updated all references throughout the project

It also made the following terminology alignment:

• Fixed all titles to use "Relying Party Provider Backend" instead of "Relying Party Backend"
• Updated section headers to use consistent terminology

For achieing that, it has:

• Moved Erasure Endpoint from provider backend file to remote flow endpoints file
• Replaced detailed sections with references to avoid duplication
• Simplified Request URI and Status Endpoint descriptions (removed detailed method/status lists)
• Applied descending headers (^) to included files for proper editorial hierarchy

Files Modified

• relying-party-endpoints.rst (EN/IT) - New parent files
• relying-party-remote-flow-endpoints.rst (EN/IT) - Renamed and updated
• relying-party-provider-backend-endpoint.rst (EN/IT) - Updated titles and references
• endpoints.rst (EN/IT) - Updated includes
• how-to-read-spec.rst (EN/IT) - Updated references
• Multiple other files - Updated references to renamed files

[Copilot]

Pull Request Overview

This PR restructures the Relying Party endpoints documentation to resolve issue #862 by creating a hierarchical structure with proper terminology alignment between EN/IT versions. The main purpose is to eliminate content duplication and organize endpoints logically.

Key changes include:

• Restructured documentation hierarchy with a new parent endpoints file
• Updated terminology to consistently use "Relying Party Provider Backend" instead of "Relying Party Backend"
• Reorganized endpoint documentation into separate files for remote flows and provider backend endpoints

Reviewed Changes

Copilot reviewed 21 out of 21 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
docs/*/relying-party-endpoints.rst	New parent files providing overview and including child endpoint files
docs/*/relying-party-remote-flow-endpoints.rst	New files containing remote flow endpoints and erasure endpoint documentation
docs/*/relying-party-provider-backend-endpoint.rst	Updated files with provider backend endpoints and terminology fixes
docs/*/relying-party-endpoint.rst	EN version removed, IT version updated with new structure and terminology
docs/*/endpoints.rst	Updated includes to reference new parent endpoint file
Multiple reference files	Updated cross-references to point to new file structure

Comments suppressed due to low confidence (1)

docs/it/relying-party-remote-flow-endpoints.rst:1

• Grammatical error: 'carried fulfilled' should be 'fulfilled'.

.. include:: ../common/common_definitions.rst

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

Grammatical error: 'carried fulfilled' should be 'fulfilled'.

Suggested change

	- The request could not be carried fulfilled due to invalid authentication by the User.
	- The request could not be fulfilled due to invalid authentication by the User.