SqlServer rule V-41402 should be an instance role

[General-Fault]

Describe the bug
SqlServer resource rule V-41402 is currently categorized as a "Database" role rule. However the settings, unless I'm misunderstanding how they work, are applied to the database instance.

To Reproduce

1. Create a basic configuration containing a SqlServer resource with the SqlRole = "Database" and the instance and any database name.

Configuration TestConfig {
    Import-DscResource -ModuleName 'PowerSTIG' -ModuleVersion '4.3.0'

    Node localhost {
      
        SqlServer DatabaseSettings {
            SqlVersion = '2016'
            SqlRole = 'Database'
            StigVersion = '1.19'
            ServerInstance = '.\DatabaseInstance'
            Database = 'master'
        }
    }
}

2. Compile the configuration TestConfig -Verbose
3. Open the resulting MOF file and find rule V-41402.
4. Note that the database name is not used in the DSC get/set/test scripts (other than as recently added in a comment for issue Conflict when configuring multiple databases #647).

[erjenkin]

Hello @General-Fault ,

Thanks for the issue. I agree with you on this issue being an 2012 SQL Instance STIG, but DISA has released this as a DB rule, which is why we parsed it as such. The checktext clearly states that traceID's on the instance will be listed, not database.

Check Text: Check to see that all required events are being audited.
From the query prompt:
SELECT DISTINCT traceid FROM sys.fn_trace_getinfo(0);
All currently defined traces for the SQL server instance will be listed. If no traces are returned, this is a finding.

I don't believe this is an issue with PowerSTIG because this settings is configured and the trace id's are listed correctly via the method listed in DISA's rule

SELECT DISTINCT traceid FROM sys.fn_trace_getinfo(0);

[General-Fault]

I'm happy with just having this case to document the issue. Especially as it pertains to case #647.