fix(buds): v-if/v-else adjacency in BUDImpactedReposDialog

Vite's Vue compiler rejected the no-matches placeholder because the
literal '.' between the inline v-if span and the v-else span counted
as a text node, breaking the v-if/v-else adjacency rule. Move the
two variants into <template v-if> / <template v-else> wrappers so
the directive pair sits on directly adjacent siblings with no
intervening text. Vue 3 template-compile rule — both branches still
render the same wording, only the wrapping element changes.

Found at runtime while testing the integration branch — would have
blocked the picker from rendering whenever the filter input matched
zero repos or no repos were tracked yet.

Signed-off-by: Arun Rajkumar <mickyarunr@gmail.com>

Author: mickyarun

frontend/src/components/buds/BUDImpactedReposDialog.vue

@@ -63,9 +63,12 @@
           v-if="!visibleRepos.length && !retiredRows.length && !trackedReposLoading"
           class="text-caption text-medium-emphasis text-center py-6"
         >
-          No tracked repos match
-          <span v-if="filter">"<code>{{ filter }}</code>"</span>.
-          <span v-else>Add a repo in Settings first.</span>
+          <template v-if="filter">
+            No tracked repos match "<code>{{ filter }}</code>".
+          </template>
+          <template v-else>
+            No tracked repos yet. Add a repo in Settings first.
+          </template>
         </div>
         <div v-else class="bud-impacted-repos__list">
           <v-checkbox