Make VPC module outputs accessible to root module

[ajp-lqx]

Summary

When creating additional resources to exist alongside the jx-provisioned resources, it's often necessary to access VPC details such as subnet IDs in order to place those resources in the same VPC. It would be great to add outputs to the eks-jx and eks-jx.cluster modules to be able to access the VPC module outputs from the root module via module.eks-jx.vpc.

Steps to reproduce the behavior

Currently the outputs from the AWS VPC module are inaccessible.

Expected behavior

When cloning the EKS infra repository, being able to access all VPC outputs by simply using module.eks-jx.vpc.<some output field>.

Module version

v1.9.0

[jenkins-x-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://jenkins-x.io/community.
/lifecycle stale

[jenkins-x-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Provide feedback via https://jenkins-x.io/community.
/lifecycle rotten