Fix resourceName used in auth check for SupervisorsTable in SystemSchema

[maytasm]

Description

SupervisorsTable in SystemSchema (powering queries to the sys.supervisors table) was using the topic/stream of the supervisorSpec as the resourceName to authenticate against. This is wrong and is inconsistent with other APIs that uses the datasource name of the supervisor (i.e. updating supervisor spec, suspending/starting, querying, etc). This change fixes this to use the datasourceName and add test to verify that only datasourceName is use as resourceName in authentication.

This PR has:

• been self-reviewed.
  • using the concurrency checklist (Remove this item if the PR doesn't have any relation to concurrency.)
• added documentation for new or modified features or behaviors.
• a release note entry in the PR description.
• added Javadocs for most classes and all non-trivial methods. Linked related entities via Javadoc links.
• added or updated version, license, or notice information in licenses.yaml
• added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
• added unit tests or modified existing tests to cover new code paths, ensuring the threshold for code coverage is met.
• added integration tests.
• been tested in a test Druid cluster.

[FrankChen021]

the java doc of orignial getSource says:

  /**
   * This API is only used for informational purposes in
   * org.apache.druid.sql.calcite.schema.SystemSchema.SupervisorsTable
   *
   * @return source like stream or topic name
   */
  String getSource();

Since here we' re using getDataSource I think we should remove the original getSource method definition. I check the code, besides the SystemSchema, there're few references in the the kafka supervisor spec, which can be replaced by calling getIoConfig().getStream()

[maytasm]

I don't think that's possible. getIoConfig is not a method of SupervisorSpec. It is only available in some (but not all) sub classes like KafkaSupervisorSpec but not CompactionSupervisorSpec. I think we still need this method