Implement `racks` module

[cmeissner]

Preflight checks

• I agree to follow the Code of Conduct.
• I have searched the issue tracker for a feature requests that matches the one I want to file, without success.
• I only submit one single feature per feature request.

Feature description

Since version 1.5, exists an API endpoint to read and write rack entities.

$ curl -sk -XGET -H "phpipam-token: ${PHPIPAM_TOKEN}" ${PHPIPAM_API_URL}/tools/racks/ | jq '.data[]'
{
  "id": "1",
  "name": "1_north_1_east",
  "size": "42",
  "location": null,
  "row": "1",
  "hasBack": "0",
  "topDown": "1",
  "description": null,
  "customer_id": null
}

To be complete in covering all available controllers with a separate module, we could take the opportunity to implement the rack module.

Proposed solution

The implementation needs some int, strings and two entities (location & customer_id) which need to be resolved. The logic for resolving the entities to it's IDs is already there.

Alternatives solution

No response

Additional context

No response

[cmeissner]

Unfortunately, there is no customers controller to manage customer data via API; hence, it is not possible to resolve a customer name to an ID, as we prefer to do in all our modules.

In phpipam/phpipam#4496 such a controller was requested, tbh in a very limited way for a feature request, but it was already recorded.

Suggestions could be to either implement the module with no support for customer linkage or to postpone the implementation.

I did not expect a quick implementation of a customer controller by @phpipam, but I like to be surprised.