Allow options like metrics, logs, tags, and tracing to work with externally defined Rest APIs for the AWS provider

Is there an existing issue for this?

• I have searched existing issues, it hasn't been reported yet

Use case description

I would like to use some of the AWS provider's features for Rest APIs that are managed through updateStage for externally defined Rest APIs.

The protection in updateStage that guards against any of these features being used when the Rest API is externally defined seems very blunt given that some (perhaps all or most) of the features are stage-specific.

I would like to be able to enable all these options for an externally defined Rest API.

I am creating a basic Rest API and logging role externally so that the Rest API id remains stable even if the serverless project's stack is torn down, so that consumers can use the Rest API id, for example to create IAM policies. However, all other management of the Rest API is done through the serverless project.

Proposed solution (optional)

Make everything work normally for externally defined Rest APIs and add a note to the documentation about items that impact the Rest API as a whole versus those that impact just the stage