[GraphQl] Custom attribute aggregations should return store specific option values

[magento-engcom-team]

Steps to reproduce:

1. Create multiple stores with multiple store views ( for example: english and arabic storeviews) and choose either the English or the luma default store as the store view
2. create a custom attribute that is visible in search and layered navigation. ( For test purpose, a drop down custom attribute " brand" with atleast couple options for different storeviews.
   For example: defaultBrand, englishBrand, arabicBrand etc)
3. Add the custom attribute to attribute set
4. Create a product and assign it to a category
5. Use the below query to query for the product and aggregrations.

{
    products(filter: {
      		category_id: {eq: {$categoryId}},
    },
      pageSize:1,
      sort:{name:DESC})
  {
    items{
      id
      sku
      name
    }
    aggregations{
      label
      attribute_code
      count
      options{
        label
        value
        count
      }
    }
  }
}
{code}
Make sure no store code is passed in through the header.
Notice that the option value returned is the "arabicBrand"
Now remove this option from the attrribute form and re-run the query, you will see that the next option value : "englishBrand" now shows up and so on

Expected:
1. Since no store code is specified, the attribute option value for the default store should be returned( if store_code is passed in, appropriate option value should be returned)

Actual:
The last eav*attribute_option_value is always returned, since store*code is not honored.
{code:php}
"aggregations" :<
{...}
{...}
    {
          "label": "brand",
          "attribute_code": "brand",
          "count": 1,
          "options": [
            {
              "label": "arabicBrand2",
              "value": "44",
              "count": 1
            }
          ]
        }
>

[m2-assistant]

Hi @magento-engcom-team. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, please, review the Magento Contributor Assistant documentation.

Please, add a comment to assign the issue: @magento I am working on this

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[m2-assistant]

Hi @pmarjan. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
     Details

     If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.
• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
     Details

     - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
     - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
     - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[m2-assistant]

Hi @gallyamov. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
     Details

     If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.
• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
     Details

     - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
     - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
     - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[magento-engcom-team]

Hi @magento-engcom-team. Thank you for your report.
The issue has been fixed in #28647 by @gallyamov in 2.4-develop branch
Related commit(s):

• 5294b5d63f673a7ac26c24fd47a2181e2f1dd499
• 9d99f172221e2939ccc42378387fd9e1ba2d85f5
• 1787ee281112d46dd9625443e0d872ece2068d4c
• f54b149eacc6fe501737596f368571662266df6b
• 68f8c779a5efb860cb183462fa809a1f90faa85e
• ddaed608ebfac94b16b0419bacf8a7f7328412db

The fix will be available with the upcoming 2.4.1 release.