SqlScript: Should Be Cluster Aware

Details of the scenario you tried and the problem that is occurring:
When the xSQLServerScript resource is applied to all of the nodes in a Failover Cluster Instance (FCI), all of the nodes will connect to the instance and ensure the desired state is true even if the node is not currently hosting the instance.

The DSC configuration that is using the resource (as detailed as possible):
When the following configuration is applied to two or more nodes in a FCI.

xSQLServerScript 'RunSQLScript-AsUSER'
{
    ServerInstance       = 'localhost\SQL2016'

    SetFilePath          = 'C:\DSCTemp\SQLScripts\Set-RunSQLScript-AsUSER.sql'
    TestFilePath         = 'C:\DSCTemp\SQLScripts\Test-RunSQLScript-AsUSER.sql'
    GetFilePath          = 'C:\DSCTemp\SQLScripts\Get-RunSQLScript-AsUSER.sql'
    Variable             = @("FilePath=C:\temp\log\AuditFiles")

    PsDscRunAsCredential = $WindowsCredential
}

Version of the Operating System, SQL Server and PowerShell the DSC Target Node is running:
Any

What module (SqlServer or SQLPS) and which version of the module the DSC Target Node is running:
Any

Version of the DSC module you're using, or 'dev' if you're using current dev branch:
Any

Start by locating the xSQLServerScript resource and reproduce the provided configuration on multiple nodes in a Failover Cluster Instance. The completed behavior should ensure the desired state only through the node currently hosting the SQL Server instance, rather than having every node connect and apply the resource.