[Bug]: Specs can fail to load examples when compiled from outside spec folder

[timotheeguerin]

Describe the bug

Specs can fail to load examples when compiled from outside the spec folder (e.g. tsp compile path/to/spec), but succeed when compiled from inside the spec folder (e.g. cd path/to/spec; tsp compile .).

Related: microsoft/typespec#2241, https://github.com/Azure/typespec-azure-pr/issues/3182

Reproduction

$ gh repo clone azure/azure-rest-api-specs
$ cd azure-rest-api-specs
$ npm ci

$ npx tsp compile specification/oracle/Oracle.Database.Management
warning @azure-tools/typespec-autorest/example-loading: Skipping example loading from examples/2023-09-01-preview because there was an error reading the directory.

$ cd specification/oracle/Oracle.Database.Management
$ npx tsp compile .
<no warning>

Checklist

• Follow our Code of Conduct
• Check that there isn't already an issue that request the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion.
• The provided reproduction is a minimal reproducible example of the bug.

[markcowl]

est: 5

[markcowl]

Describe the breaking change
Many specs in azure-rest-api-specs configure a relative path to examples, which prevents compilation outside the spec directory. Adds a new setting that enforces absolute path, deprecates the old setting and adds a default so that no setting is required in most cases.

Back-compat design to avoid immediate breaking
Existing setting is deprecated and a default is added, so the setting will not be required for most specs going forward.

All existing specs are corrected.

Impact
This change affecting:

• ARM
• Data-plane
• Existing specs: approx. # of service/spec impacted: ~30
• New specs
• Emitters
• SDK

Targeted Sprint
Sprint:

Additional information
Requested by the engineering team