issue: #2294

<img width="904" alt="image"
src="https://github.com/user-attachments/assets/291fc961-84e7-465d-9c48-4f0f4f78af06"
/>

…6267)

issue: #5465
### Example
```typespec

 @doc("""
    Format of the redacted output. Only valid when Operation is Redact. 
    Please refer to https://learn.microsoft.com/en-us/azure/healthcare-apis/deidentification/redaction-format for more details.
    """)
  redactionFormat?: string;
```


## Previously
```csharp
  ///<summary>
  /// Format of the redacted output. Only valid when Operation is Redact.  Please
  /// Format of the redacted outpu
  /// Format of the redacted output. Only valid when Operation is Redact.  P
  /// ils.
  ///</summary>
  [TypeSpec.Helpers.JsonConverters.StringConstraint(MinLength = 1, MaxLength = 16)]
  public string RedactionFormat { get; set; }
```

## Now
```csharp 
///<summary>
/// Format of the redacted output. Only valid when Operation is Redact.  Please
/// refer to
/// https://learn.microsoft.com/en-us/azure/healthcare-apis/deidentification/redaction-format
/// for more details.
///</summary>
  [StringConstraint( MinLength = 1, MaxLength = 16)]
  public string RedactionFormat { get; set; }
```

Fixes #1848 

Link to typespec azure changes:
Azure/typespec-azure#2322

---------

Co-authored-by: Christopher Radek <Christopher.Radek@microsoft.com>

First step in figuring out what should be internal, this will also help
in the future to prevent exposing new types by mistake

This convert the export * to named exports so we can get a manifest of
what is exported. **This pr shouldn't remove anything**

---------

Co-authored-by: Mark Cowlishaw <markcowl@microsoft.com>

The relative wasn't correct when nested folder in the path. I was
overprocessing the path. Fixing this

Co-authored-by: Christopher Radek <Christopher.Radek@microsoft.com>

fix #5687

Features
- respect the `packageManager`(Format `<packageManager>@<version>` or
`<packageManager>@<version>+<algo>.<hash>`) and
`devEngines.packageManager` field
- packages are be downloaded from the public npm registry
-no support yet for proxy, private registries, using the node route is
always available for those cases
- ability to save a hash of the packagemanager in the field which is
used to validate the `.tgz` file match.
- new flag `--save-package-manager` which populate the `packageManager`
field with the resolved version and the hash.


Only support `npm` for now. Adding support for `yarn` and `pnpm` should
be quite simple.

---------

Co-authored-by: Christopher Radek <14189820+chrisradek@users.noreply.github.com>

Upgrade to alloy 0.6.0

Impacted packages:
@typespec/http-client
@typespec/emitter-framework
@typespec/http-client-js

Changes are around formatting leveraging the new formatting capabilities
from allo such as <For>, <StatementList>, <List>

We'll truncate mock test class name when the file path is too long. This
will result in a duplicate file path in edge cases:

https://dev.azure.com/azure-sdk/internal/_build/results?buildId=4623919&view=logs&j=83516c17-6666-5250-abde-63983ce72a49&t=c10d5f44-55ce-55d7-7975-407ed75d9a96&l=40534

The failure is usually due to Java syntax problem. We want to print the
file name and content for better diagnostics.

Sample output of this PR.

```
[main] ERROR com.microsoft.typespec.http.client.generator.TypeSpecPlugin - Failed to format file 'src/main/java/azure/clientgenerator/core/usage/implementation/ModelInOperationsImpl.java'
177:15: error: illegal unicode escape
174 
175     /**
176      * Serialize the 'OrphanModel' as request body.
177      * data\userdomain
178      * 
179      * Expected body parameter: 
180      * ```json
```

I've also add logic to parse the JAR output to diagnostics/trace for
tsp.


![image](https://github.com/user-attachments/assets/180cebb0-de05-4094-8820-7d34928d7615)


![image](https://github.com/user-attachments/assets/4b8b12e9-1bad-489e-bdeb-93ff485f9347)

autorest.java Azure/autorest.java#3035

…oute` (#6326)

#6311 switched openapi3 to use `HttpProperty` instead of
`HttpOperationParameter`. The `@typespec/rest` package did some
filtering of parameters under a couple conditions (including path
constants) that wasn't applied to properties. This caused an extra path
parameter to be emitted in OpenAPI3 (and typespec-autorest when
eventually applying the same changes there).

This PR applies the same `@autoRoute` parameter filtering to properties.

---------

Co-authored-by: Christopher Radek <Christopher.Radek@microsoft.com>