Remove heartbeatId from receipt.json

[amarthadan]

When working on api3dao/old-api3-docs#825 I've noticed that we store heartbeat ID in the receipt.json even though it's just a copy of the heartbeat ID from config.json. To add to the confusion, we send that ID with the heartbeat with the name deployment_id. I propose removing the hearbeatId field from the receipt.json (and with it the whole api section as it will become empty).

[bbenligiray]

As per yesterday's call we're planning to autogenerate the heartbeat ID similar to Lambda function names

[amarthadan]

Is there a task for that? But in that case, we would probably want to keep the heartbeat ID in the receipt, right?

[bbenligiray]

@aquarat was supposed to create a few tasks out of that call, I'm not sure if he did it yet. Not sure about the receipt question.

[martinkolenic]

Hi, I've done this to test it:

• turn on heartbeat in config and deploy the coingecko-signed-data example
• check that the heartbeat ID is not present in receipt.json
• do the same for an older version and check that the ID is actually present as control

Everything worked in line with expectations.