feat: add symbol/replace

[DivyanshuVortex]

Resolves #8479

Description

This pull request implements the RFC for introducing the package assert/has-split-symbol-support.

The implementation follows the structure and conventions of similar existing packages:

• assert/has-iterator-symbol-support
• assert/has-is-concat-spreadable-symbol-support
• assert/has-has-instance-symbol-support

Summary of changes

• Added a new assertion utility to detect support for Symbol.split.
• Copied the base implementation from assert/has-iterator-symbol-support.
• Updated all identifiers from iterator → split.
• Implemented correct detection logic for Symbol.split.
• Added tests, examples, and benchmarks, modeled after existing stdlib packages.
• Verified all tests and benchmarks pass locally.

No additional functional differences exist beyond checking for Symbol.split.

---

Related Issues

• Resolves [RFC]: add symbol/replace #8479

---

Questions

No questions for reviewers at this time.

---

Other

No additional notes or screenshots required.
Implementation follows stdlib package conventions.

---

Checklist

• Read, understood, and followed the contributing guidelines.

---

AI Assistance

Did you use AI assistance?

• Yes
• No

If yes, how?

• [] Code generation (implementation guidance)
• [] Test/benchmark generation
• Documentation (including examples)
• Research and understanding

Disclosure

I consulted GPT for guidance and clarity on stdlib patterns while preparing this PR.
All final implementation code and decisions were authored manually.

---

@stdlib-js/reviewers

[stdlib-bot]

Coverage Report

Package	Statements	Branches	Functions	Lines
symbol/replace	$\color{green}110/110$ $color{green}+100.00%$	$\color{red}2/3$ $color{green}+66.67%$	$\color{green}0/0$ $color{green}+100.00%$	$\color{green}110/110$ $color{green}+100.00%$

The above coverage report was generated for the changes in this PR.

[DivyanshuVortex]

“Hey @kgryte, I went through the development guide, but I’m still unable to resolve the body issue in the test lint rule. Could you please take a look?”

[kgryte]

@DivyanshuVortex This is not how we write tests. Please follow the style that we use throughout the project. That you deviated from that style is why CI is currently failing.

[kgryte]

Suggested change

	* This symbol specifies the method that replaces matched substrings and is used
	* by `String.prototype.replace()` to delegate replacement behavior to an object.
	*

[kgryte]

We do not line wrap descriptions.

[kgryte]

This is not how our READMEs are structured. Please follow that structure exactly. It is not clear why you removed the typical import statement, the typical heading, etc. The original RFC suggested simply copy-pasting and then tweaking. Here, you decided to deviate from project conventions.

[kgryte]

Left initial comments.

[kgryte]

Ref: a68d5d9

[stdlib-bot]

Thank you for working on this pull request. However, we cannot accept your contribution as the issue this pull request seeks to resolve has already been addressed in a different pull request or commit.

Thank you again for your interest in stdlib, and we look forward to reviewing your future contributions.