Remove camelcase-keys, replace with inline utility

[ryancbahan]

Summary

• Add camelcase-keys.ts (~40 lines) in app-logs/ with parity behavior to the npm package
• Handles: snake_case, kebab-case, deep recursion, leading underscore stripping, ALL_CAPS normalization, Date/non-plain-object preservation
• Update 4 import sites (poll-app-logs.ts, utils.ts, and their test files)
• Remove camelcase-keys from packages/app/package.json

Test plan

• 16 parity tests covering all edge cases
• All 57 app-logs tests pass

[ryancbahan]

• Remove is-interactive, inline the TTY check #7198
• Remove http-proxy-node16, replace with lightweight inline proxy #7196
• Remove network-interfaces, use os.networkInterfaces() directly #7195
• Remove camelcase-keys, replace with inline utility #7194 👈 (View in Graphite)
• Remove ansi-colors, replace with lightweight inline utility #7193
• Remove tmp and @types/tmp dependencies #7192
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[github-actions]

We detected some changes at packages/*/src and there are no updates in the .changeset.
If the changes are user-facing, run pnpm changeset add to track your changes and include them in the next release CHANGELOG.

Caution

DO NOT create changesets for features which you do not wish to be included in the public changelog of the next CLI release.

[gonzaloriestra]

We already have a similar function in cli-kit. If you need anything else, I think we should add it to that file.

[ryancbahan]

Happy to follow up on this, but i think we should prioritize shipping this to support the supply chain remediation project

[gonzaloriestra]

Well, camelcase-keys is pinned to a specific version that we have been using for a long time, so it doesn't look urgent.

[isaacroldan]

I agree with Gonzalo here, we can use the one from cli-kit. No need to add 2 new files with 100+ changes for something that already exists :thinking_face:
An agent can quickly update this PR to use the camelize function from cli-kit, I don't think there is that much urgency to remove this dependency that prevents us to doing it the right way!

[ryancbahan]

I'll update this to use camelize. The urgency here is founded IMO -- the js community has had two major supply chain attacks in two weeks. Removing deps is a company-wide effort right now, and the cost of consolidation is cheap in comparison. That being said, it's fair feedback that we can just do the centralization now.

[ryancbahan]

@gonzaloriestra true, but we don't always use --frozen-lockfile and minor version resolutions can transitively lead to major version changes in other deps

[github-actions]

Differences in type declarations

We detected differences in the type declarations generated by Typescript for this branch compared to the baseline ('main' branch). Please, review them to ensure they are backward-compatible. Here are some important things to keep in mind:

• Some seemingly private modules might be re-exported through public modules.
• If the branch is behind main you might see odd diffs, rebase main into this branch.

New type declarations

We found no new type declarations in this PR

Existing type declarations

packages/cli-kit/dist/public/node/monorail.d.ts

@@ -66,10 +66,6 @@ export interface Schemas {
             cmd_app_linked_config_uses_cli_managed_urls?: Optional<boolean>;
             cmd_app_warning_api_key_deprecation_displayed?: Optional<boolean>;
             cmd_app_deployment_mode?: Optional<string>;
-            cmd_app_validate_json?: Optional<boolean>;
-            cmd_app_validate_valid?: Optional<boolean>;
-            cmd_app_validate_issue_count?: Optional<number>;
-            cmd_app_validate_file_count?: Optional<number>;
             cmd_dev_tunnel_type?: Optional<string>;
             cmd_dev_tunnel_custom_hash?: Optional<string>;
             cmd_dev_urls_updated?: Optional<boolean>;