NAS-139116 / 25.10.2 / Add hosts allow/deny fields to SMB share purposes (by william-gr)

[bugclerk]

Automatic cherry-pick failed. Please resolve conflicts by running:

git reset --hard HEAD~1
git cherry-pick -x bc0f3bc93ae63fef00f3ecd923d49884b10a751c
git cherry-pick -x 8af299a05b5e586b63c8968ce731110caca7a709

If the original PR was merged via a squash, you can just cherry-pick the squashed commit:

git reset --hard HEAD~1
git cherry-pick -x 28b31646e2977348697abc8ccd0e1c970429369d

Changes:

Testing:

Verify both fields are visible and can be entered/edited.

Downstream

Affects	Reasoning
Documentation	Add back hosts allow/deny to smb shares
Testing	Add back hosts allow/deny to smb shares

Original PR: #13051

[bugclerk]

Jira URL: https://ixsystems.atlassian.net/browse/NAS-139116

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
⚠️ Please upload report for BASE (stable/goldeye@b66c4cf). Learn more about missing BASE report.
✅ All tests successful. No failed tests found.

Additional details and impacted files

@@                Coverage Diff                @@
##             stable/goldeye   #13056   +/-   ##
=================================================
  Coverage                  ?   86.18%           
=================================================
  Files                     ?     1826           
  Lines                     ?    67316           
  Branches                  ?     8070           
=================================================
  Hits                      ?    58013           
  Misses                    ?     9303           
  Partials                  ?        0           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[AlexKarpov98]

@william-gr seems like something is wrong here.
.yarn/cache

[bugclerk]

This PR has been merged and conversations have been locked.
If you would like to discuss more about this issue please use our forums or raise a Jira ticket.