Refactor PUT endpoints to use id in route and DTO in body

Refactored update (PUT) endpoints in multiple controllers to accept the record id as a route parameter and the update data as a DTO in the request body. Updated method signatures, XML documentation, and imports to align with RESTful conventions and improve API clarity. Controller methods now construct command objects using the id and DTO before sending to MediatR.

src/ReC.API/Controllers/ProfileController.cs

@@ -1,5 +1,6 @@
 using MediatR;
 using Microsoft.AspNetCore.Mvc;
+using ReC.Application.Common.Procedures.UpdateProcedure.Dto;
 using ReC.Application.Profile.Commands;
 using ReC.Application.Profile.Queries;
 
@@ -32,14 +33,15 @@ public class ProfileController(IMediator mediator) : ControllerBase
     /// <summary>
     /// Updates a profile via the PROFILE update procedure.
     /// </summary>
-    /// <param name="procedure">UpdateProfileProcedure payload.</param>
+    /// <param name="id">The identifier of the PROFILE record to update.</param>
+    /// <param name="data">UpdateProfileProcedure payload.</param>
     /// <param name="cancel">A token to cancel the operation.</param>
     /// <returns>No content on success.</returns>
-    [HttpPut]
+    [HttpPut("{id:long}")]
     [ProducesResponseType(StatusCodes.Status204NoContent)]
-    public async Task<IActionResult> Put([FromBody] UpdateProfileCommand procedure, CancellationToken cancel)
+    public async Task<IActionResult> Put([FromRoute] long id, [FromBody] UpdateProfileDto data, CancellationToken cancel)
     {
-        await mediator.Send(procedure, cancel);
+        await mediator.Send(new UpdateProfileCommand() { Id = id, Data = data }, cancel);
         return NoContent();
     }