Remove duplicate DLP API calls

[jjnesbitt]

Here's a screen grab of the network panel when loading the Dandiset Landing Page. Notice all of the duplicate calls

These should be investigated and removed.

[waxlamp]

@DeepikaGhodki, I think you should work on this to get some familiarity with the DLP (dandiset landing page) code; @mvandenburgh, if you could pair with Deepika to provide a quick tour and any necessary mentorship, that would be great.

[DeepikaGhodki]

I was going through the DLP code, documenting my initial findings here:

3 calls to /versions on page load

• watchEffect (watching on all states) (fetchDandiset that calls the above API)
  One obvious fix would be to remove watchEffect and watch on a specific state. (This change was made in Navigation buttons on landing page #1172)

• watch on props.identifer results in remaining 2 (initializeDandiset)
  This remaining extra call is attributed to getting the data corresponding to latest version. It is a two step process, where first we get the count of versions and then fetch the last one. We can either get the latest version directly from the server or access the versions[] state from the store.

Would like to dig deeper into the logic for initialising dandiset with most recent version, but would love to hear your comments or any historical reasons for multiple calls during initialization.

TBD: /info

[dandibot]

🚀 Issue was released in v0.2.43 🚀