Backend: Add components field to ciCatalogResource GraphQL query

Summary

From a discussion in #415657 (comment 1565164770), the intention of this issue to create a backend components field within the ciCatalogResource GraphQL query.

Proposal

query getCiCatalogResourceDetails($id: CiCatalogResourceID!) {
  ciCatalogResource(id: $id) {
   version { #this is new
    components{ # This is new.
      nodes{
        id 
        name
        path # This is the link to include the component, like: `gitlab.com/gitlab-org/dast@~latest`
        inputs{ # The component inputs so we can build the table
          nodes{
            name # We call this "parameters" when building the table, but this is the name of the input argument. Feel free to rename to what make sense to the API
            defaultValue # Should this be always a string? In the FE at least we are going to cast it, but perhaps for cosistency we'd be better off returning the actual ruby value?)
            required # Let's get a Boolean here, on the FE we are going to convert it to "Yes" or "no"
          }
        }
      }
    }
    }
  }