Refactor config struct for 1:1 config to project

[zlesnr]

Objective

Currently, the tutone generate.yml configuration is meant to be run 1:1 per package. After some deliberation, it seems like having a single config file for a given project might make more sense as we look to increase the scope of what tutone is doing.

One example proposal here is to leverage something like this:

packages:
  - name: alerts
    path: pkg/alerts
    types:
      - name: AlertsMutingRuleConditionInput
      - name: AlertsMutingRuleInput
      - name: AlertsPoliciesSearchCriteriaInput
      - name: AlertsPoliciesSearchResultSet
      - name: AlertsPolicy
      - name: AlertsPolicyInput
      - name: AlertsPolicyUpdateInput
      - name: AlertsNrqlConditionTermsOperator

Note that we have a series of packages (very go centric) where we can specify the name, and a path, and a list of types that we should filter down to. Then we can update the one configuration file to manage all the packages for a given project.

The above does not have to be the final solution, but removing the need to have a config per package makes some amount of sense here.

[zlesnr]

I believe this is complete.