need APIs for all ping result data and data with computeBudget (default now at moment) and without computeBudget

Migrating from InfluxCloud to Influx Enterprise, ping-api influx does not work.
The issue is because Influx Enterprise only support int64 data type. The issue is described as follow
influxdata/influxdb#7804
We need the convert uint64 to int64.
We won't lose data because the value of data is not excess the limit of int64.

When run report service / workers in multiple clusters, there are data are missing in the report.

Devnet received the following information
{"code":-32002,"message":"Transaction simulation failed: Attempt to debit an account but found no record of a prior credit.","data":{"accounts":null,"err":"AccountNotFound","logs":[],"unitsConsumed":0}}(75)}

Check confirm status interval is in sec. This is not sensitive enough in low traffic time.

use "-" in tag and field does not follow naming convention

Adding processed status in error message helps us to understand where the transaction lost occur

When the failover alert channel become public, the token may leak because endpoint in current code contains token.
The endpoint url and token should be store in different variable so that when alert is sent, only the endpoint url is sent.

We need alerts which one is based on ping results from tx with compute fee and one without compute fee.
This is related to the issue solana-labs/solana#29023

Push ping result to influxdb and show in Grafana Dashboard.

When slack and discord alert both are enabled.
Slack and discord should both receive an alert but discord does not receive an alert.

Problem

rpc token shows in some errors which is not a typical error so it does not filter out by short() function.
The token should be hided

Possible solution

Filter out error messages before message is sent

Current wait_time is
waitTime := cConf.ClusterPing.PingConfig.MinPerPingTime - (result.TakeTime / 1000)

However, this does not consider addRecord (add to database time).
This can be significant.

Issue

On Sunday, Apr 10 around 12:00 UTC, the cluster is running well, but the Solana Ping Stats chart shows many errors.

In comparison, the validators.app Ping Thing shows average confirmation times, from 3 points on the cluster, of around 5 seconds.

Source: https://www.validators.app/ping-thing

I believe the low success rate shown on the explorer is due to the TX retry strategies used on the ping client or the RPC node.

A TX is valid for up to 150 blocks after the submitted block hash. -- about 60-75 seconds on a wall clock. So, the 35-second WaitConfirmationTimeout threshold may be too short (depending on your retry strategy).

Suggestion

• Retry TXs from the client or the RPC node every 2 seconds until confirmation or the block hash expires.
• Increase WaitConfirmationTimeout to 60 or 75 seconds (or rely on the block hash expiration error).

To compare compute fee effect to ping time.
with and without compute fee needs to be in the same server .
Because it seems locality affect results.

Pager duty has moved from slack to alert so ping-api service should support discord alert.

Currently the service uses trace log or trace failover alert to track current endpoint.
A quick way should be provided to check current endpoint

gorm support concurrent goroutine, so mutex is not necessary and it reduce the performance