Local DynamoDB streams Integration

[dakota002]

Resolves #2804

This PR adds @nasa-gcn/architect-plugin-dynamodb-local-streams as a dependency, updates the app.arc, and adds a few other changes to configure the testing environment to work both with a local docker instance for dynamodb and the table-streams functionality.

There is a known issue with the docker dynamodb local image that I have described in the readme of this package. https://github.com/nasa-gcn/architect-plugin-dynamodb-local-streams
But it does not impede our development. In short, the first invocation for each stream will throw a TrimmedDataAccessException. This is expected and is intentionally suppressed and logged in the console. Subsequent invocations run as expected.

In order to fully set this up, you must add the following to your .env:

ARC_TABLES_PORT=8000
ARC_DB_EXTERNAL=true

To Test:

• Make sure docker is running.
• Install new packages:

npm i

• Run dev

npm run dev

Current Streams that can be invoked:

• Circulars
  • New circulars, edit both will trigger the stream
• Synonyms
  • Need to enable the SYNONYM feature flag.
  • Create new synonyms through the Synonym Moderation feature

[codecov]

Codecov Report

Attention: Patch coverage is 0% with 7 lines in your changes missing coverage. Please review.

Project coverage is 6.29%. Comparing base (016d123) to head (e9ca2ea).

Files with missing lines	Patch %	Lines
app/lib/email.server.ts	0.00%	7 Missing ⚠️

Additional details and impacted files

@@           Coverage Diff            @@
##            main   #2918      +/-   ##
========================================
- Coverage   6.30%   6.29%   -0.01%     
========================================
  Files        175     175              
  Lines       4348    4353       +5     
  Branches     474     474              
========================================
  Hits         274     274              
- Misses      4072    4077       +5     
  Partials       2       2              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[lpsinger]

See nasa-gcn/architect-plugin-dynamodb-local#6 (comment).

[dakota002]

See nasa-gcn/architect-plugin-dynamodb-local#6 (comment).

I left a response there, but I am going to track this as a further enhancement to the plugin. It requires more work, but doesn't hold up reaching this goal

[lpsinger]

See nasa-gcn/architect-plugin-dynamodb-local#6 (comment).

I left a response there, but I am going to track this as a further enhancement to the plugin. It requires more work, but doesn't hold up reaching this goal

We need to add some more items for this to our development instructions, don't we?

[dakota002]

See nasa-gcn/architect-plugin-dynamodb-local#6 (comment).

I left a response there, but I am going to track this as a further enhancement to the plugin. It requires more work, but doesn't hold up reaching this goal

We need to add some more items for this to our development instructions, don't we?

Yea, I can update the docs for that

[lpsinger]

What do the changes in this file have to do with the DynamoDB simulator?

[dakota002]

When you trigger the lambda, it tries to send an email, which can fail if either the template is not defined (which it isnt on local, thats a sandbox thing I believe) or if the user doesn't have valid credentials and pointing to a matching env (which would be the case for running playwright tests)

Also I am working on resolving the currently failing tests locally, should have that out later

[lpsinger]

Looks like you're still working on fixing the playwright tests?

[lpsinger]

Also, please resolve merge conflicts.