Inconsistent way of defining repository objects

[exalate-issue-sync]

h3. As a user

I want to have a consistent experience with regards to how objects are created and imported from Git repositories
So that it’s clear what is imported and why

h3. Description

Currently, most of the objects imported to Infrahub from an external repository requires the users to specify them within a .infrahub.yml file. The exception to this are GraphQL queries, it’s enough to have files within the repositories that have the {{.gql}} extension. As these files could be deeply nested there’s no good way for a user to know what GraphQL queries will be imported when adding a repository, also the behaviour is inconsistent.

h3. Acceptance Criteria

When a repository is added or synced with Infrahub. Then only GraphQL queries defined within a .infrahub.yml file should be imported or synced. Any {{.gql}} files not defined by .infrahub.yml should be ignored.