How to handle two dependent Issues, but unique from a workflow perspective

Two Scrum tasks.

Both in the same project

Both dependent on each other (i.e. both must complete within the Sprint)

But both have completely different work flows.

Should they reside in different Jira projects?

Or, perhaps, one should be given a different Issue Type to map it to its unique Workflow?

Although Scrum suggests the cross-functional team, in reality there is an SME team focussed on specific infrastructure tasks (such as building out new AWS environments) that the application feature team will never touch, and vice versa.

My initial thoughts are:

• Keep them in one JIRA project (as its all contained in one Sprint) and rely on the tasking out of an individual Product Backlog Item, when produce sub-tasks, to assign the work;  but can there be different types of sub-task each with its own workflow?

JIRA version is 5.1 / JIRA Agile is being used.