glue: ability to specify a custom bucket to store glue scripts & extra "py" filess/zips

### Describe the feature

Currently CDK puts all assets in the CDK asset bucket, however this causes some issues with my developers being able to see the job up in the glue console. And I don't want to give them access to the CDK bucket. I'd rather, instead, want to specify an override location for JUST those two assets (the main py script for the glue job and the packaged extra "py" files) to an alternate bucket (e.g. the glue scripts bucket).

### Use Case

Have some separation of the glue scripts to a separate bucket for clean isolation and easier permission handling.

### Proposed Solution

I originally tried to see if I could CDK a policy with read access to those assets, however the asset objects in CDK do not provide a means to get the final URL out of them.

IMHO simply allowing an override for the asset objects to specify an alternate bucket would provide way to accomplish this. Additionally providing the means to obtain a value to be used in a policy (resources) to grant READ access would be helpful as well.

### Other Information

_No response_

### Acknowledgements

- [x] I may be able to implement this feature request
- [ ] This feature might incur a breaking change

### AWS CDK Library version (aws-cdk-lib)

2.174.0 (have also dug through 2.194 as well, but had to downgrade at the time due to the glue revamp not supporting all functionality at the time)

### AWS CDK CLI version

2.1016.0

### Environment details (OS name and version, etc.)

macOS python 3.10.18

Start by tracing how AWS CDK handles Glue job assets and the CDK asset bucket in the aws-cdk-lib source. Review the asset objects and policy-resource behavior described in the issue. Done means Glue scripts and extra Python files can target a separate bucket and expose values suitable for granting read access, with tests covering the new behavior.

Written by the indexing model from the issue text.