PATCH for Bulk Operations

[clundie-CL]

Problem description
Related to review comments included with PR #73

The API currently uses the PATCH method for bulk insert, remove, and replace operations on resource relationships. For example:

PATCH /devices/{deviceId}/isolated-networks  # Bulk update networks
PATCH /isolated-networks/{netId}/devices     # Bulk update devices

According to CAMARA guidelines, PATCH should only be used to modify the resource itself, not to manage relationships between resources. Using PATCH in this way can lead to confusion and non-standard API behavior.

Expected behavior
The API should use POST and DELETE methods for managing relationships between resources. For example:

POST /devices/{deviceId}/isolated-networks    # Add networks
DELETE /devices/{deviceId}/isolated-networks  # Remove networks

# Add multiple networks
POST /devices/{deviceId}/networks
Content-Type: application/json
{
  "networkIds": ["net1", "net2"]
}

# Remove multiple networks
DELETE /devices/{deviceId}/networks
Content-Type: application/json
{
  "networkIds": ["net3", "net4"]
}

This approach aligns with CAMARA guidelines and standard RESTful practices.

Alternative solution
If bulk operations are required, perhaps consider using batch endpoints with POST and DELETE, or provide separate endpoints for each operation type, while still avoiding PATCH for relationship management.

Additional context
This issue was identified during the CAMARA design review. Aligning HTTP method usage with CAMARA guidelines will improve API clarity, interoperability, and ease of client implementation.

[clundie-CL]

Would need to consider different path hierarchy relationships for addressing this. For example: #75 (comment)

That would imply that the following path may not exist and need to think about obtaining equivalent functionality in a different way.

PATCH /isolated-networks/{netId}/devices