Add support for associating teams to functionalities in the catalog

[michaelmosher]

Currently, the firehydrant_functionality resource supports specifying services associated with a functionality, but it doesn't support specifying teams. Likewise, the firehydrant_functionality data resource returns information about services but not teams.

Use-cases

I would like to configure my org's catalog with IAC – the documentation of team ownership in particular is a significant portion of the value I see the catalog providing. Without this feature, I can create functionalities in the catalog, but I will then need to manually modify each in order to define their owners and responding teams.

Attempted Solutions

Mostly just abandoning IAC for functionalities.

That said, the FireHydrant API already supports owner and teams for functionalities (as documented here, here, and here), which means I could probably use another provider like Mastercard/restapi to address this instead, but I haven't actually attempted to do so.

Proposal

The firehydrant_service resource and data-source already provides a template for these new attributes:

• owner_id - (Optional) The ID of the team that owns this service.
• team_ids - (Optional) A set of IDs of the teams responsible for this service's incident response.

In fact, it seems that in large part, those implementations could be copied, as well (here, for example).