DEVDOCS-6713 - Clarify resourceId construction from filterName in product filter translations (#1244)

<!-- Ticket number or summary of work -->
# [DEVDOCS-6713]


## What changed?
<!-- Provide a bulleted list in the present tense -->
* Clarify that `resourceId` values are constructed from `filterName`
values in the product filter translations query section
* Add concrete example showing how `brand` `filterName` becomes
`bc/store/productFilters/brand` `resourceId`
* Update callout and description to explicitly explain the relationship
between `filterName` and `resourceId`

## Release notes draft
<!-- Provide an entry for the release notes using simple, conversational
language. Don't be too technical. Explain how the change will benefit
the merchant and link to the feature.

Examples:
* The newly-released [X feature] is now available to use. Now, you'll be
able to [perform Y action].
* We're happy to announce [X feature], which can help you [perform Y
action].
* [X feature] helps you to create [Y response] using the [Z query
parameter]. Now, you can deliver [ex, localized shopping experiences for
your customers].
* Fixed a bug in the [X endpoint]. Now the [Y field] will appear when
you click [Z option]. -->
* Improved clarity in the product filter translations documentation. The
query section now clearly explains how to construct `resourceId` values
from `filterName` values, making it easier to query translations for
specific product filters.

## Anything else?
<!-- Add related PRs, salient notes, additional ticket numbers, etc. -->

This change resolves confusion about the relationship between
`filterName` and `resourceId` when querying product filter translations.

ping @jamesqquick @bc-terra 

[DEVDOCS-6713]:
https://bigcommercecloud.atlassian.net/browse/DEVDOCS-6713?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ

---------

Co-authored-by: Terra Hyde <terra.hyde@bigcommerce.com>

Author: chris-nowicki

docs/store-operations/translations/filters.mdx

@@ -19,12 +19,6 @@ The product filter translatable fields are:
 | Category, Brand, Variants, Custom Fields, Price, Rating | Display Name as the field name (e.g. `brand` or `category`) |
 | Other Filters | Display Name as `display_name` <br /> Has Free Shipping as `has_free_shipping` <br /> Is Featured as `is_featured` <br /> In Stock as `in_stock` |
 
-<Callout type='warning'>
-While most translatable entities use a `resourceId` format of `bc/store/{{type}}/{id}}`, product filters use a different format.
-
-Use `bc/store/ProductFilters/{filterName}`, using the filters above for reference.
-</Callout>
-
 <Callout type='info'>
 Only string values are translatable. Numeric content such as product count or price values are not translatable.
 </Callout>
@@ -97,10 +91,10 @@ query {
 ### Query a translation by `resourceId`
 
 <Callout type='warning'>
-When querying a translation by `resourceId`, you must provide the full `resourceId` in the format `bc/store/product-filter/{filter_id}`.
+When querying by `resourceId`, the `resourceId` value must be constructed from the `filterName` using the format `bc/store/productFilters/{filterName}`. For example, the `filterName` `brand` becomes the `resourceId` `bc/store/productFilters/brand`.
 </Callout>
 
-This query returns translation(s) by `resourceId`.
+This query returns translation(s) filtered by `resourceId`. For product filters, the `resourceId` is constructed from the `filterName` as shown in the callout above.
 
 <Tabs items={['Request', 'Response']}>
 <Tab>