chore: fix release-please detection of lookup commits

[BethGriggs]

Setting lookup: commits to hidden resulted in no changelog changes, meaning we'd still need wait for a user-facing commit to trigger the release PR (or push an empty fix commit).

For now it seems easier to just include lookup: PRs in the changelog. Or, we could consider hiding those updates under <details> sections in the CHANGELOG as a post-step release-please workflow?

Checklist

• documentation is changed or added
• contribution guidelines followed
  here

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 96.20%. Comparing base (45ba271) to head (00ba057).

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1146   +/-   ##
=======================================
  Coverage   96.20%   96.20%           
=======================================
  Files          29       29           
  Lines        2213     2213           
=======================================
  Hits         2129     2129           
  Misses         84       84           

☔ View full report in Codecov by Harness.
📢 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.

[richardlau]

For now it seems easier to just include lookup: PRs in the changelog. Or, we could consider hiding those updates under <details> sections in the CHANGELOG as a post-step release-please workflow?

I think it kind of depends what changed. I would treat new modules being added to lookup as minor and probably worth mentioning in the changelog.

[BethGriggs]

Hmmm, checking some documentation on release please now as I don't think this will do what we want
Let's try it

[BethGriggs]

#1147 did get opened as expected

I think it kind of depends what changed. I would treat new modules being added to lookup as minor and probably worth mentioning in the changelog.

For those I think we can use feat(lookup): add.... It means we're really just treating lookup: as a conventional alternative to fix(lookup). Probably okay, I was just trying to account for the habit of using lookup: for flakes/skips/etc.