CSV export for Assets

[Ashesh3]

Frontend PR: coronasafe/care_fe#6262

Summary

This PR introduces several changes to the Asset model and its related serializers and viewsets in the care/facility app. The primary goal is to improve the handling of asset types and statuses, and to support CSV export of asset data.

Changes

Asset Model

• The AssetType and Status enums are now defined outside the Asset model, and their choices are generated separately as AssetTypeChoices and StatusChoices.
• Reversed mappings for asset types and statuses are created for use in CSV exports.
• A CSV_MAPPING dictionary is added to map model fields to human-readable CSV headers.
• A CSV_MAKE_PRETTY dictionary is added to provide functions for converting database values to human-readable strings for CSV exports.

Asset Serializer

• The status and asset_type fields now use the StatusChoices and AssetTypeChoices generated outside the Asset model.

Asset ViewSet

• The list method is overridden to support CSV export of asset data. If the CSV_REQUEST_PARAMETER is present in the request, the method generates a CSV file with headers and values based on the CSV_MAPPING and CSV_MAKE_PRETTY dictionaries in the Asset model.

Testing

Please ensure that these changes do not break existing functionality, particularly around the handling of asset types and statuses. Also, please test the new CSV export functionality and ensure that the exported data matches the specified mappings and transformations.

Closing

These changes should improve the flexibility and usability of the asset management features in the care/facility app. Please review and provide any feedback.

[Ashesh3]

Tests passing locally:

----------------------------------------------------------------------
Ran 116 tests in 7.164s

OK