FeatureStore create_dataset() does not support cross-account Feature Store (shared Glue database name mismatch)

**Description**

When using SageMaker Feature Store in a cross-account setup, create_dataset() fails because it assumes the Glue database name returned from the Feature Group description is directly usable in the consumer account.

In cross-account architectures, this assumption breaks.

**Details**

- Feature Groups are owned in a source account
- Offline store is accessed from a consumer account via a shared Glue database
- The Feature Group description returns the database name from the source account
- The shared Glue database name in the consumer account is different
- create_dataset() retrieves the database name directly from the Feature Group description without any way to override or remap it:

As a result, create_dataset() queries a database that does not exist in the consumer account.

**Expected behavior**

The SDK should support cross-account Feature Store usage by allowing:

- A database name override, or
- A mapping mechanism for shared Glue databases

从 FeatureStore create_dataset() 开始，跟踪它如何从 Feature Group 描述中获取 Glue 数据库名称。将该值与 consumer account 中使用的共享数据库名称进行比较，然后确定应如何表示所请求的 override 或 mapping。完成的标准是，跨账户数据集创建可以指向 consumer 数据库，并且相关测试覆盖了该行为。

由索引模型根据 Issue 内容生成。