Allow github action integration to sync multiple infisical folders

[jrdn91]

Feature description

Currently, connecting multiple github actions integrations with different infisical folder to a single environment in my github actions works initially, but making a change to any of the ENV's causes only the ones in that folder to stay synced and the others go away.

Why would it be useful?

Currently, we are using github actions to build and s3 sync our react app to a bucket, this action needs some VITE ENV's and github actions need some AWS related ones to authenticate to AWS etc.

We also have another action that will build and sync a docker image to ECS which doesn't need any of the ENV's related to the app running in the docker, but will need the same AWS related ones to sync with AWS.

We would like to have the "common" AWS related ENV's in a folder to essentially be synced on it's own and then separately sync the folder for the front end app ENVs to the same github action environment without any of them being removed when one changes

Additional context

Currently the way to do this is to put all ENV's that we want in the github environment into a single folder and only sync that one folder to the one environment. It MAY also be advantageous to keep the "common" AWS ENV's in it's own project if they are shared between multiple projects and then have the project related ENV's also be able to sycn to the same github environment. We intend to set up our infra in this way soon for all internal dev builds as apposed to having separate accounts for each project. So it would be way quicker to be able to have a setup like this.