feat: make analysis buttons open workflow landing pages (#137)

[hunterckx]

• No error handling for the API request
• Only regulation is set up

[mvdbeek]

Pretty cool thank you!

[mvdbeek]

This is going to vary across workflows, I suppose

Suggested change

	request_state: { reference_genome: string };
	request_state: { [key: string]: string }:

would be the right interface ?

[mvdbeek]

Suggested change

	return WORKFLOW_LANDING_URL_PREFIX + encodeURIComponent(id);
	return `${WORKFLOW_LANDING_URL_PREFIX}${id}?public=true;

UUIDs shouldn't need uri encoding, so I dropped that here, but of course no harm doing it anyway.

[hunterckx]

@mvdbeek Thanks for the feedback! I've:

• Updated the types to make more room for alternative keys (though in a different way than suggested -- I wanted to make it explicit what the keys can be)
• Added public: true to the API request body
• Added ?public=true to the constructed landing page URL (but left the URL encoding in -- although it's not necessary in theory, I'm inclined to be cautious and default to encoding things when constructing URLs)

[NoopDog]

@hunterckx, can you rebase this, please? Thanks!

[mvdbeek]

We're expecting the full TRS url here, which is the TRS id and the version.

[mvdbeek]

For right now this is working well. I have a few things to build on here, could we get this merged ?