I don't think this is possible, because the trust policy is an integral part of the role, and the role resource can only be part of one Pulumi stack. There are two solutions to this: Either you can re-arrange the resources (or create multiple roles) so that this problem does not occur, or you have to update the first stack after the second stack has been deployed.
Without knowing anything about your application, from an AWS IAM perspective I'd say that the first option is the recommended one. You can create all policies in the first stack, and then create a dedicated role to assume for each of the resources/principals you create in the second stack and attach the policies to them. This gives you central control over permissions, while giving each principal a tightly scoped role to assume.