chore: upgrade to Go 1.22 (celestiaorg#1249)

## Motivation

Part of celestiaorg#1248
We want to cut a release of celestia-core with Go 1.22 support to enable
celestia-node to bump to Go 1.22.

## Description

1. Upgrade to Go 1.22
2. Bump pyroscope deps
3. Copy over golangci-lint config from CometBFT v0.34.x branch
4. Resolve a few lint issues by copying code from CometBFT v0.34.x
branch

fix: use genesis file app version if it is set (backport celestiaorg#…

…1227) (celestiaorg#1232)

feat: export `ErrTimedOutWaitingForTx` (celestiaorg#1169)

Closes celestiaorg#1168

Revert "fix!: change the instrumentation config to circumvent viper b… (

celestiaorg#1167)

…ug (celestiaorg#1143)"

This reverts commit f1dc8f7.

which is a breaking change to the config

fix: catch context errors from http provider (backport celestiaorg#1160…

…) (celestiaorg#1164)

This is an automatic backport of pull request celestiaorg#1160 done by
[Mergify](https://mergify.com).
Cherry-pick of 52633f4 has failed:
```
On branch mergify/bp/v0.34.x-celestia/pr-1160
Your branch is up to date with 'origin/v0.34.x-celestia'.

You are currently cherry-picking commit 52633f4.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   light/provider/http/http.go

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   light/provider/http/http_test.go

```


To fix up this pull request, you can check it out locally. See
documentation:
https://docs.github.com/en/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

---


<details>
<summary>Mergify commands and options</summary>

<br />

More conditions and actions can be found in the
[documentation](https://docs.mergify.com/).

You can also trigger Mergify actions by commenting on this pull request:

- `@Mergifyio refresh` will re-evaluate the rules
- `@Mergifyio rebase` will rebase this PR on its base branch
- `@Mergifyio update` will merge the base branch into this PR
- `@Mergifyio backport <destination>` will backport this PR on
`<destination>` branch

Additionally, on Mergify [dashboard](https://dashboard.mergify.com) you
can:

- look at your merge queues
- generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com
</details>

---------

Co-authored-by: Callum Waters <cmwaters19@gmail.com>

feat: more precise mempool metrics (celestiaorg#1158)

## Description

This PR introduces more precise mempool metrics to provide a clearer
view in why txs are getting evicted or failing

fix(types): Implement nil check on commit.ValidateBasic (celestiaorg#…

…1094)

Found in celestia-node header validation check. If a malformed
`ExtendedHeader` with a nil Commit is broadcasted through the network,
it would cause recipients to panic. We decided the check belongs in core
as ValidatorSet also does a nil check.

Update rpc client header (#9276) (#9349) (celestiaorg#1096)

## Description

cherry picks the cherry pick to get the header back
celestiaorg@d95e437

closes celestiaorg#1095

---------

Co-authored-by: Callum Waters <cmwaters19@gmail.com>
Co-authored-by: samricotta <37125168+samricotta@users.noreply.github.com>

feat: add time to `RequestPreparePropsosal` (celestiaorg#1081)

## Description

Adds the last commit median time to `RequestPreparePropsosal`. This
allows the application to accurately calculate the spendable funds of
vesting accounts, since this is the time used when executing the
transactions and when evaluating the propsoal during `ProcessProposal`.

The height was also added, but it doesn't have to be since the
application can calculate that value. That value is also passed in other
versions of comet, and we'll have to add it we want to unfork from the
sdk so I figured why not. Happy to remove it as well.

Release v0.38.0