Eng 1391 fix aws auth issue for customer (#2607)

The error messaging behaviour can be seen
[here](https://linear.app/overmind/issue/ENG-1391/fix-aws-auth-issue-for-customer#comment-60549ad7).

GitOrigin-RevId: 790885003ffce8121547a9d9412b6b1bdb7bfaec

stdlib: remove query args and fragments from redirect URLs (#2598)

This will reduce the number of random redirect-to-oauth items, which
provide no value to the blast-radius. The trade-off is that we now might
be missing some valid redirect chains that would require the args to
pass through.

GitOrigin-RevId: c897427fe3cdbef7dfcac3647c0e39c8c52eb6f0

Hide test-changes from customers (#2585)

This change
* add changes.is_system flag, that will be true when a change should not
be shown in the app
* update all relevant SQL statements
* set is_system when storing a change as part of blast radius llm
testing
* remove obsolete change metering in stripe
* update area51 to show the new flag
* add link to original change (without database consistency to avoid any
interference with regular operations)

GitOrigin-RevId: 462a1444b76bfeeedc7b150edfa4b8f4da0df42f

fix, cli submit signal match start/end change permissions (#2572)

GitOrigin-RevId: 471e8f0b045080d1ddadd89e7767bc7c099932a3

Add GCP Dataplex Data Scan adapter (#2549)

## Summary
- Creates new adapter for Dataplex data scans
- Supports GET and SEARCH operations with location-based queries
- Defines blast propagation rules for Dataplex entities and storage
resources
- Includes terraform mapping support

GitOrigin-RevId: c5f6e05282f76d45e45aface0eebbb3eb1259f60

Added unique scope to all terraform items (#2233)

This will be replaced with the real GUN if it gets mapped, but if not
we'll get a truly unique path

GitOrigin-RevId: 0eaaa13a87dd63ac7240d9b5de1f5a64bd4fe2c7

Fixed a number of mappings that were wrong (#2216)

This was causing even more mapping issues for customers

GitOrigin-RevId: e96ba6628b998adedba03e9d56ddcc3c305d3434

feat, adding signal settings to sdp and api-server (#2195)

also does
https://linear.app/overmind/issue/ENG-934/implement-signals-settings

I was not around when the KV store was done for account config, it looks
weird how is uses atlas/sqlc

So my outstanding questions is how do you want to handle default values.
1. what are the default values i took them from the ticket
2. do we want to set the default values for all accounts in the DB, or
do what we currently do which is, unless the value is set in the DB, we
just give the system defaults.
3. when retrieving the signal settings if they dont exist, i save them
to the account. (mimicking the HCP behaviour)

GitOrigin-RevId: 7d528add288ffd489774a808dc5c4effe1e1ec74

feat, initial commit of signals to SDP. simple storage, aggregation o…

…f signals and caching (#2181)

and
https://linear.app/overmind/issue/ENG-931/create-full-signal-aggregation-function

GitOrigin-RevId: 22c367522912192bacfe9b8cdfa151d01e0cf6de

fix gcp adapter, add missing err check (#1530)

GitOrigin-RevId: 7a27f14997b4d195f856270a7cc655deb622af41