Convert rest.ts to composition API

[mvandenburgh]

The rest module seems to be blocking the upgrade to Vue 3; in Vue 2, it was possible to initialize a Vue object as follows:

const dandiRest = new Vue({
	data() {
		return { user: null }
	},
	...
});

And then access a data object like this:

console.log(dandiRest.user)

But, the equivalent Vue 3 code doesn't work:

const dandiRest = Vue.createApp({
	data() {
		return { user: null }
	},
	...
});

console.log(dandiRest.user) // doesn't work

I'm not sure what the issue is or how it was changed, but I can't even find the docs that specified this behavior for Vue 2. I'd be curious to hear if anyone has any ideas why that is. But regardless, converting to Composition API avoids this issue and is also something we've planned for a long time, so I just went ahead and did that.

Fixes #1267

[mvandenburgh]

Note, this function is redundant now that we're using composition API. I made the necessary updates to the rest of the codebase to account for the fact that this is a Ref instead of a function.

[jjnesbitt]

Is there a particular reason to keep the dandiRest object? Or is it just a matter of PR scope? I think we could remove the wrapping entirely and just have all those functions at the top level of rest.ts.

[jjnesbitt]

Looks good, tested locally. My only concern would be my other comment, but I still think we could merge this aside from that.

[mvandenburgh]

Is there a particular reason to keep the dandiRest object? Or is it just a matter of PR scope? I think we could remove the wrapping entirely and just have all those functions at the top level of rest.ts.

Sorry, I thought I added a comment describing that but clearly I didn't. Yes, I left the dandiRest object to keep the scope of this PR minimal. Changing it would require touching a significant amount of the frontend code base, so I figured that could be left for a follow up PR while this PR only concerns itself with the core options => composition API conversion.

[dandibot]

🚀 PR was released in v0.3.67 🚀