Propagate the Profiler changes to the documentation

What

Add the metadata fields to all the profiler calls in the documentation and use Read_profiler everywhere

Why

Because these changes were added in the code but never propagated to the documentation Read_profiler was declared then Profiler was used instead, making it confusing (because it was a mistake)

How

Manually testing the MR

Checklist

• Document the interface of any function added or modified (see the coding guidelines)
• Document any change to the user interface, including configuration parameters (see node configuration)
• Provide automatic testing (see the testing guide).
• For new features and bug fixes, add an item in the appropriate changelog (docs/protocols/alpha.rst for the protocol and the environment, CHANGES.rst at the root of the repository for everything else).
• Select suitable reviewers using the Reviewers field below.
• Select as Assignee the next person who should take action on that MR