Followed the steps at https://github.com/Azure/azure-sdk-for-js/wiki/Samples-v2-Migration-Guide
/cc @willmtemple 

Note: I moved browserSamples and expressSamples into the generated v5 samples folder since dev-tool doesn't work with those.

to delete tags before delete the image as this is the recommended best
practice for the service.

* [Identity] Test improvements

* temporary node 16 fix

* Since unhandled promise rejections are not supported in Node 16, tickAsync can't be awaited

* fix the test

Co-authored-by: Harsha Nalluru <[email protected]>

## What

- Regenerate from 7.3-preview swagger
- Add `getRandomBytes` method

## Why

- For July we would like to add support for the RNG endpoint in a Managed HSM. While this is a customer ask for Java, we will add this to all languages at the same time.

As part of AzureSDKAutomation#7022, we will be moving the version of `@types/node` from 8 to 12
This PR has the changes required to fix the build errors that occurred when trying out this change
- The [Agent](https://nodejs.org/docs/latest-v12.x/api/http.html#http_class_http_agent) class in Node.js 12 has an extra property `maxTotalSockets`. The docs say there is a default value for this, but it it is still marked as a mandatory property in the types. We use our own interface for this class for the purposes of user providing their own custom agent. Am casting it in this PR to the expected type. If anyone has better ideas here, am all ears :)
- `global.URL` is not a thing as per the types for Node.js 12. We needed this to support Node.js 8
- Fixing the types for `port` in the parsed url

The actual move to v12 for `@types/node` will be done in a separate PR

* Use BufferEncoding as encoding is not a string in Node.js 12

* Fix typing issue for fsStat returning unknown

* adds simple background refresh

* Adds setInterval with unref

* cleanup

* wip prenock

* wip

* Removes recorder, fixes timeout in tests

* extract api

* fix lint

* format

* Adds flag

* lint

* Fix parition spelling

* modify endpoint check

* fix tests

* Comment proxy

* adds back copyright

* skip session spec

* Fix session token

* Fix session spec on emulator

* Support track2 management packages

Perf test packages should not be using the eslint plugin

Fixes the below error

```


ESLint couldn't find the plugin "@azure/eslint-plugin-azure-sdk".

(The package "@azure/eslint-plugin-azure-sdk" was not found when loaded as a Node module from the directory "/home/vsts/work/1/s/sdk".)

It's likely that the plugin isn't installed correctly. Try reinstalling by running the following:

    npm install @azure/eslint-plugin-azure-sdk@latest --save-dev

The plugin "@azure/eslint-plugin-azure-sdk" was referenced from the config file in "../../../.eslintrc.json".

```

…est-pipeline (Azure#16045)

This PR updates the newly added `@azure-rest/core-client-paging` package to use the same version of `@azure/core-rest-pipeline` that the other packages use.

We recently GA'd (on main, not released yet) version 1.1.0 of `@azure/core-rest-pipeline` and want to keep everyone on the latest version.

Follow up for Azure#16046 to fix the resulting linter errors

…16010)

Update to latest core packages and improve pipeline robustness.

As part of the development of the new pipeline, event grid was hand
ported to use the new pipeline. Now that the code generator targets
the new pipeline, we can start using it to generate the code.

Since EventGrid includes the `/api/events` path segment in the
Endpoint, We need to do a small amount of post processing of the
generated code, to ensure `/api/events` is not appended to the
endpoint (we do this by setting an empty path in the operation spec,
which is as things were before moving over to the generator).

Fixes Azure#15823

…me environments (Azure#15937)

…dential (Azure#15856)

* [Identity] Add support for Bridge to Kubernetes to ManagedIdentityCredential

* one very simple test

* forgot this line

…ers (Azure#15932)

* [Monitor Exporter] Separate tests into internal and public folders

* fix build

* put tests in internal

* prettier

* console log for testing

* testing

* format

* console

* try flush processor

* format

* remove console logs

## What

- Adds warning filter to ignore known rollup warnings that are safe to ignore
- Ignore `this has been rewritten to undefined` in synapse
- Ignore circular dependencies in synapse

## Why

These are both known warnings, are safe to ignore, and add noise to the build output unnecessarily. 

The first is totally safe to ignore:

```
var __spreadArray = (this && this.__spreadArray) || function (to, from) {
```

Is emitted from TypeScript in the OTel ESM and is safe to use.
The second is a known issue in OTel 1.0.0 that is not harmful at runtime.

Finally, we have precedent for doing the exact same thing in other packages like service-bus.

The watchful eyes of @vishnureddy17 found that we still have reference to Node.js 8 in our Contributing Guide!!

This PR fixes that.

Related to AzureSDKAutomation#7022

* Update identity to 2.0.0-beta.4 for quantum jobs

* Fix CI Errors

* Fix CI Errors

Based on the Retry-After specification, 503 should also be supported when considering the Retry-After header.

This also aligns with upcoming Identity plans.

…ure#16049)

close Azure#13814

…5853)

This PR enables PKCE on the InteractiveBrowserCredential.

We don’t have tests for this yet. I’ll make sure to test it manually, at least.

Fixes Azure#15168

…ludeVisualization option. (Azure#16058)

* Big update to use the latest stable swagger files for all of the Log Analytics services. Each reference is by git commit ID this time to prevent any accidental drift.

Also, added in the includeRender header (via the `includeVisualization` option).

Fixes Azure#15771

* Fixing codeowners to reflect the proper owners for the package:
@KarishmaGhiya - main owner
@maorleger - backup owner

* Formatting!

…ease. (Azure#16072)

* Convenience Method to create a synonymmap object

* Update sdk/search/search-documents/src/synonymMapHelper.ts

Co-authored-by: Jeff Fisher <[email protected]>

* Fix for PR Comments

Co-authored-by: Jeff Fisher <[email protected]>

* [Identity] InteractiveBrowserCredential LoginHint

* formatting

* Update CHANGELOG.md

* Bring changes from JS docs metadata

* Move business logic inside Update-DocsMsMetadata.ps1

* Update with the latest changes in JS PR

* Update from latest PR feedback

* Add check for empty path to prevent crashes when creating relative paths

Co-authored-by: Daniel Jurek <[email protected]>

This PR just updates the release dates for core releases that I plan to release:

- @azure/core-tracing
- @azure/core-http
- @azure/core-rest-pipeline
- @azure/core-client
- @azure/core-lro
- @azure/core-auth

- Switch to using rest instead of cli for querying work items
  as cli is limited to 1000 items only.
- Fix issues with Generated fields not being set.
- Correctly sort older workitems by version isntead of string.

Co-authored-by: Wes Haggard <[email protected]>

* [event-hubs] add AmqpAnnotatedMessage support

* undo experimental deletion of decode method from service bus

* address feedback

See Azure#16094 for details. This PR just updates core-client to 1.2.1 so I can release it

The release pipeline complains if there are empty sections in the changelog. Removing the empty section to correct this and unblock core-http release.

* Disable release date check

* Release check is not finding release date

Co-authored-by: Praveen Kuttappan <[email protected]>

For 1.2.0 release

It consists of the following already-reviewed PRs:
Azure#16114
Azure#16095
Azure#15995
Azure#15684
Azure#15649
Azure#15598
Azure#15554

…entCredentials (Azure#15837)

This PR adds `tenantId` to the `getTokenOptions`, and adds options on every Identity credential to allow multi-tenant authentication (which will be disabled by default).

Fixes Azure#15797

* Increment package version after release of azure-core-tracing

* Increment package version after release of azure-core-lro

* Increment package version after release of azure-core-rest-pipeline

* Run rush update

Co-authored-by: Maor Leger <[email protected]>

* Increment package version after release of azure-core-http

* Increment package version after release of azure-core-client

…ete (Azure#15989)

Fixing an issue where we could lose messages or provoke an alarming message from rhea (`Received transfer when credit was 0`)
    
The message loss issue is related to how we trigger 'drain' using 'addCredit(1)'. Our 'receiver.drain; receiver.addCredit(1)' pattern actually does add a credit, which shows up in the flow frame that gets sent for our drain. This has led to occasionally receiving more messages than we intended.
    
The second part of this was that we were masking this error because we had code that specifically threw out messages if more arrived than were requested. If the message was being auto-renewed it's possible for the message to appear to be missing, and if we were in receiveAndDelete the message is effectively lost at that point. That code is now removed (we defer to just allowing the extrra message, should a bug arise that causes that) and we log an error indicating it did happen.
    
The rhea error message appeared to be triggered by our accidentally allowing multiple overlapping 'drain's to occur (finalAction did not check to see if we were _already_ draining and would allow it to happen multiple times). Removing the concurrent drains fixed this issue but I didn't fully investigate why.

Fixes Azure#15606, Azure#15115