[other] check in new release files

[bredmond5]

Pull Request Template

Description

previous pr #1075

I didnt understand that i was supposed to do this before, updated now

Fixes # (issue)

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• Unit test
• Integration test

JS Budget Check

Please mention the size in kb before abd after this PR

Files	Before	After
dist/build.js.
dist/build.min.js

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules
• I have checked my code and corrected any misspellings

Mentions:

List the person or team responsible for reviewing proposed changes.

cc @BranchMetrics/saas-sdk-devs for visibility.

[github-actions]

Test Results

  1 files  ±0    1 suites  ±0   51s ⏱️ -2s
159 tests ±0  152 ✅ ±0  7 💤 ±0  0 ❌ ±0 
162 runs  ±0  155 ✅ ±0  7 💤 ±0  0 ❌ ±0 

Results for commit af55c52. ± Comparison against base commit 41840c9.

♻️ This comment has been updated with latest results.

[bredmond5]

this is not how we do aws access keys, so i removed it

[gdeluna-branch]

Nit: this was released 2024-04-10

[bredmond5]

whoops good catch