feat(bounties): add inline search to mobile toolbar in IssuesList

[nickmopen]

Summary

On screens below the xl breakpoint (< 1536px), the /bounties toolbar only showed an Options button — search was hidden inside a popover requiring an extra tap. This PR adds an
always-visible inline search field to the toolbar so users can filter issues without opening the popover.

Changes in src/components/issues/IssuesList.tsx:

• Moved usePortal declaration above optionsPortalFilters so the search block can be conditionally rendered
• optionsPortalFilters: search section now renders only when usePortal is true (xl+ sidebar), removing the duplicate entry from the mobile popover
• inlineToolbar: added IssuesListSearchTextField filling available width, with the Options button pinned right
• return: moved <Card> inside <DebouncedSearchInput> so the inline search field shares the same search context

Related Issues

Closes #808

Type of Change

• Bug fix
• New feature
• Refactor
• Documentation
• Other (describe below)

Screenshots

Before — only the Options button visible in the toolbar:

After — inline search field always visible next to Options button:

Checklist

• New components are modularized/separated where sensible
• Uses predefined theme (e.g. no hardcoded colors)
• Responsive/mobile checked
• Tested against the test API
• npm run format and npm run lint:fix have been run
• npm run build passes
• Screenshots included for any UI/visual changes

[ventura-oss]

Thanks for the PR. After looking at the before/after, I don't think adding an inline search field is the right fix here.

The page already has a search bar at the top of the layout. Adding a second visually-identical search input inside the toolbar means the same view ends up with two search bars stacked one above the other, which is more confusing than the original.

The real issue with the sub-xl toolbar isn't that it lacks a search — it's that the Options button is right-aligned all by itself, which leaves a whole row of dead space to its left. This PR is filling that dead space rather than addressing it.

A better direction would be to reposition Options so the empty row doesn't exist in the first place — for example, inline with the tab row (All / Available / Pending / History), or grouped with the other header/toolbar controls — rather than introducing a duplicate search affordance to justify the row.

Happy to look at a follow-up that takes that approach.