[Patch] Added Support of requiresStreamAddress and requiresStreamParameterAddress

[rajatavams]

Adds explicit support for @requiresStreamAddress and @requiresStreamParameterAddresses tags in custom function metadata parsing.

Context GitHub issue #6499

• The JSON metadata schema for Custom Functions explicitly exposes requiresStreamAddress, requiresStreamParameterAddresses for streaming functions.
• However, there is no equivalent JSDoc tag; developers are expected to use @requiresAddress (or @requiresParameterAddresses) combined with @streaming to get requiresStreamAddress ( or requiresStreamParameterAddresses for streaming functions.

This update:

1. recognizes both tags directly
2. maps them to metadata options (requiresStreamAddress, requiresStreamParameterAddresses),
3. validates that these stream-specific tags are used only on streaming functions,
4. updates conflict validation/error messaging paths to include the new tags,
5. adds test coverage for valid explicit stream tags and invalid non-stream usage.
6. this does not impact existing behaviour as mentioned in the context section (@ requiresAddress / @ requiresParamterAddress + @ Streaming = requiresStreamAddress / requiresStreamParamterAddress) to ensure backward compatibility.

Do these changes impact command syntax of any of the packages?
No.

Do these changes impact documentation?
Need to add @ requiresStreamAddressand @ requiresStreamParameterAddresses in Supported JSDoc Tags List.

Validation/testing performed:

Ran package tests in custom-functions-metadata with npm test.
Result: 137 passing.

Manual Testing Done Via custom-functions-metadata generate command.

[rajatavams]

@rajatavams please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.

@microsoft-github-policy-service agree [company="{your company}"]

Options:

• (default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.

@microsoft-github-policy-service agree

• (when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.

@microsoft-github-policy-service agree company="Microsoft"

Contributor License Agreement

@microsoft-github-policy-service agree company="Microsoft"

[millerds]

/azurepipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[millerds]

Looks like the package-lock file is not correct.

[rajatavams]

/azurepipelines run

[azure-pipelines]

Commenter does not have sufficient privileges for PR 977 in repo OfficeDev/Office-Addin-Scripts

[rajatavams]

/azurepipelines run

[azure-pipelines]

Commenter does not have sufficient privileges for PR 977 in repo OfficeDev/Office-Addin-Scripts

[millerds]

/azurepipelines run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[millerds]

@rajatavams you have to be part of the DevX group in order to trigger the automation (which would also trigger automatically if you were part of the group).

Looks like the lock file still needs correct updating.