Move website_name column into columnSet

[bradleyfrye]

Description (*)

One column was outside the columnset in this layout, for some reason. Moving this so the grid shows the user's website name.

Fixed Issues (if relevant)

Manual testing scenarios (*)

1. In admin, go Sales > Orders, click the Create New Order button.
2. Ensure the customer grid's rightmost column is now a column with header Website, which should match up with the column set in this layout file.

Contribution checklist (*)

• Pull request has a meaningful description of its purpose
• All commits are accompanied by meaningful commit messages
• All new or changed code is covered with unit/integration tests (if applicable)
• All automated tests passed successfully (all builds on Travis CI are green)

[magento-cicd2]

All committers have signed the CLA.

[magento-engcom-team]

Hi @bradleyfrye. Thank you for your contribution
Here is some useful tips how you can test your changes using Magento test environment.
Add the comment under your pull request to deploy test or vanilla Magento instance:

• @magento-engcom-team give me test instance - deploy test instance based on PR changes
• @magento-engcom-team give me 2.3-develop instance - deploy vanilla Magento instance

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

[magento-engcom-team]

Hi @sidolov, thank you for the review.
ENGCOM-3733 has been created to process this Pull Request

[magento-engcom-team]

@bradleyfrye thank you for contributing. Please accept Community Contributors team invitation here to gain extended permissions for this repository.

[ghost]

Hi @bradleyfrye, thank you for your contribution!
Please, complete Contribution Survey, it will take less than a minute.
Your feedback will help us to improve contribution process.

[magento-engcom-team]

Hi @bradleyfrye. Thank you for your contribution.
We will aim to release these changes as part of 2.3.1.
Please check the release notes for final confirmation.

[magento-engcom-team]

Hi @bradleyfrye. Thank you for your contribution.
We will aim to release these changes as part of 2.3.1.
Please check the release notes for final confirmation.