Bump the npm-production group with 1 update (#15)

* Bump the npm-production group with 1 update

Bumps the npm-production group with 1 update: [yaml](https://github.com/eemeli/yaml).


Updates `yaml` from 2.4.0 to 2.4.1
- [Release notes](https://github.com/eemeli/yaml/releases)
- [Commits](eemeli/yaml@v2.4.0...v2.4.1)

---
updated-dependencies:
- dependency-name: yaml
  dependency-type: direct:production
  update-type: version-update:semver-patch
  dependency-group: npm-production
...

Signed-off-by: dependabot[bot] <support@github.com>

* Added ECS Metadata URL to the intercept.py  (#18)

* Added ECS Task metadata endpoint

Sometimes,  a Github Runner can run inside a ECS Task and this metadata can be used to fetch the respective Variables

Ref: https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-metadata-endpoint-v2.html

* Fix Name and Description

* updated dist

---------

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: RT <35173068+rtcms@users.noreply.github.com>
Co-authored-by: Abhishek Anand <raianand@users.noreply.github.com>

README.md

@@ -1,7 +1,7 @@
 ![Bolt](assets/imgs/bolt-header-light.png#gh-light-mode-only)
 ![Bolt](assets/imgs/bolt-header-dark.png#gh-dark-mode-only)
-## Secure Github actions with 1 line of code
-Add this step to jobs in your Github workflow file(s) to secure your runner:
+## Secure GitHub actions with 1 line of code
+Add this step to jobs in your GitHub workflow file(s) to secure your runner:
 ```yaml
   - name: Setup Bolt
     uses: koalalab-inc/bolt@v1

package.json

@@ -67,7 +67,7 @@
     "@actions/cache": "^3.2.4",
     "@actions/core": "^1.10.1",
     "@actions/exec": "^1.1.1",
-    "yaml": "^2.4.0"
+    "yaml": "^2.4.1"
   },
   "devDependencies": {
     "@babel/core": "^7.24.0",