Whenever a Backend API is create, it should get by default a "hits" metric so the user doesn't have to manually create one in order to start defining methods, just like we have always done for products.

Not having a "hits" metric by default also complicates things in case the user creates a first backend API metric named other than "hits". In this case, this first metric will be used as parent of the methods but an actual "hits" metric can still be defined afterwards. This would introduce a weird case where two different top level metrics of the backend API have child metrics but only one of them is actually the "hits" metric.

Dev Notes
Need to sync with apisonator folks about this