feat(api,ui): use feedFullName as id for data-feeds

[Tommytrg]

Update feed and result-requests collections adding a new field (feedFullName) to avoid use random generated id.
To achieve this, the following changes have been made to feed and result-requests:

feed

• feedFullName field has been added
• request field has been removed

result-requests

• feedFullName field has been added
• feedId field has been removed
• label field has been removed
• address field has been removed

Models before the migration are:

Feed {
  id: String! 
  name: String!
  address: String!
  lastResult: String
  label: String!
  network: String!
  requests: [ResultRequest]!
  color: String!
  blockExplorer: String!
}
ResultRequest {
  id: String!
  feedId: String!
  result: String!
  label: String!
  requestId: String!
  address: String!
  timestamp: String!
  drTxHash: String!
  error: String
}

Models after the migration were:

Feed {
  id: String!
  address: String!
  blockExplorer: String! 
  color: String!
  feedFullName: String!
  label: String!
  name: String!
  network: String!
}
ResultRequest {
  id: String!
  drTxHash: String!
  error: String
  feedFullName: String!
  requestId: String!
  result: String!
  timestamp: String!
}

In addtion, this PR renames network names to discern between different chains and their networks
Close #62

[aesedepece]

I have the hunch that we may want to add the number of decimal digits in the fullName, e.g. ethereum-mainnet_btc-usd_3, as I can foresee that it could happen that we publish some feed with 3 digits, then people start using, and later someone needs 6 digits, but we can't simply replace the former because it would be a breaking change.

[Tommytrg]

I have the hunch that we may want to add the number of decimal digits in the fullName, e.g. ethereum-mainnet_btc-usd_3, as I can foresee that it could happen that we publish some feed with 3 digits, then people start using, and later someone needs 6 digits, but we can't simply replace the former because it would be a breaking change.

Then, the data-feed-explorer would show two different feeds for the same one. From now on, we have this information in the contract so we can store it inresult-request its digits to avoid creating a new feed if the digits change. What do you think?

[aesedepece]

I have the hunch that we may want to add the number of decimal digits in the fullName, e.g. ethereum-mainnet_btc-usd_3, as I can foresee that it could happen that we publish some feed with 3 digits, then people start using, and later someone needs 6 digits, but we can't simply replace the former because it would be a breaking change.

Then, the data-feed-explorer would show two different feeds for the same one. From now on, we have this information in the contract so we can store it inresult-request its digits to avoid creating a new feed if the digits change. What do you think?

I mean, in that case we would definitely want to list 2 different feeds on the site.

[aesedepece]

We can't afford having to specify providers here. This should proably be on each feed's configuration or whatever, as in an ideal world, we should be able to add feeds without doing PRs, simply by modifying config files.

[Tommytrg]

We are adding it in this way because we are using providers with secrets instead of the Portainer's gateway. In other PR, we can avoid modifying this file and the provider's dictionary every time we want to support a new network.