Implement top part of token dashboard

[csillag]

The token dashboard is what we find when visiting /:network:/:runtime:/token/:address:, for example like this.

This is different from the normal account / contract page. (Although they link to each other.)

The PR implements the top and middle part of the token dashboard. The bottom part (with multiple tabs) is coming later.

Designs:

• Desktop
• Mobile

Also, when displaying info about a contract

• Properly display creator info (see the design here ) -- test with 0x301879c8677e050f0f7104fe6a3059806Abb41C6
• If the contract is about a token, link to the relevant token dashboard (see on the above visual) -- test with 0x6Cb9750a92643382e020eA9a170AbB83Df05F30B

[github-actions]

Deployed to Cloudflare Pages

Latest commit:	ddcbbcc4649f98c24c2e6d7b2a97a1631bb45808
Status:	✅ Deploy successful!
Preview URL:	https://fd2d77ae.oasis-explorer.pages.dev

[csillag]

@donouwens says:

This is correct

There will be some updates, but what we have is already worth reviewing.

[lubej]

Visual wise header looks a bit off:

[lubej]

LGTM overall

[csillag]

Visual wise header looks a bit off:

Right. Fixed (?):

[csillag]

Visual wise header looks a bit off:

Finally fixed properly:

[csillag]

This solves this issue:

[csillag]

@donouwens approves the latest iteration of UI tweaks.

[csillag]

Apparently there was some mishap here around the various commits, because it looks the the version merged is not actually the final version; probably some commits were accidentally dropped as part of a force-push. Probably nothing major, just some small cleanups. Still looking.

[csillag]

Guys, can you help me running some some analysis what happened here?

Specifically, I'm looking at these events:

In detail:

• The first event says that I have force-pushed this branch from ddcbbcc to 791dce3. This (the second one) is actually the final version.
• Then there is the approval
• Then there is the merge commit: 9227d9a

Now, of you look at the merge commit, it has this:

The first parent is the last commit on the master branch, and the second parent comes from this branch. But it is not the last commit; it the one that have been superseeded and overwritten by the first event. (You can see the git commit hashes.) So basically, even though I have pushed the latest stuff, what has been merged is not the latest stuff, but the previous one.

How is that even possible?

[csillag]

I have restored the only missing change in #655, but I still don't understand what happend, and as a result, have lost a bit of trust in GitHub.