feat(type): implemented resource type

[hamidhabib-buttons]

Implemented Resource Type data model and UI component

Description

Fixes # (266)

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• Navigate to a resource page
• Click on specific site or trail
• Check the resource type information is available

Checklist

• I have read the CONTRIBUTING doc
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have already been accepted and merged

[marcellmueller]

Nice work on this! The implementation looks sound. Just a couple thoughts:

• What was your reasoning for keeping this in the same recreation_map_feature table that the old database uses? I know Jimmy brought up just having the code on the main recreation_resource table since it's a key piece of information and just a one to one relationship.

• We still need an insert statement to import the prod data from the fta schema to our rst schema in /migrations/fta/sql/V1.0.2__fta_to_rst.sql.

[marcellmueller]

Nice work on this and thanks for the updates! 🙇