Update AzConfig release version to 1.0.1 (#7151)

* update release version

CONTRIBUTING.md

@@ -103,7 +103,7 @@ Unreleased Dependency version – Whenever possible, libraries should be using t
 
 An example of Current vs Dependency versions: `com.azure:azure-storage-blob-batch` has dependencies on `com.azure:azure-core`, `com.azure:azure-core-http-netty` and `com.azure:azure-storage-blob`. Because `com.azure:azure-core` and `com.azure:azure-core-http-netty` are both built outside of azure-storage pipeline we should be using the released or *Dependency* versions of these when they're dependencies of another library. Similarly, libraries built as part of the same pipeline, that have interdependencies, should be using the Current version. Since `com.azure:azure-storage-blob-batch` and `com.azure:azure-storage-blob` are both built part of the azure-batch pipeline when `com.azure:azure-storage-blob` is declared as a dependency of `com.azure:azure-storage-blob-batch` it should be the *Current* version.
 
-An example of an Unreleased Dependency version: Additive, not breaking, API changes have been made to `com.azure:azure-core`. `com.azure:azure-storage-blob` has a dependency on `com.azure:azure-core` and requires the additive API change that has not yet been released. An unreleased entry needs to be created in [version_client.txt](./eng/versioning/version_client.txt), under the unreleased section, with the following format: `unreleased_<groupId>:<artifactId>;dependency-version`, in this example that would be `unreleased_com.azure:azure-core;1.2.0-beta.1` (this should match the 'current' version of core). The dependency update tags in the pom files that required this dependency would now reference `{x-version-update;unreleased_com.azure:azure-core;dependency}`. Once the updated library has been released the unreleased dependency version should be removed and the POM file update tags should be referencing the released version.
+An example of an Unreleased Dependency version: Additive, not breaking, API changes have been made to `com.azure:azure-core`. `com.azure:azure-storage-blob` has a dependency on `com.azure:azure-core` and requires the additive API change that has not yet been released. An unreleased entry needs to be created in [version_client.txt](./eng/versioning/version_client.txt), under the unreleased section, with the following format: `unreleased_<groupId>:<artifactId>;dependency-version`, in this example that would be `unreleased_com.azure:azure-core;1.2.0` (this should match the 'current' version of core). The dependency update tags in the pom files that required this dependency would now reference `{x-version-update;unreleased_com.azure:azure-core;dependency}`. Once the updated library has been released the unreleased dependency version should be removed and the POM file update tags should be referencing the released version.
 
 ### Tooling, version files and marker tags
 

eng/jacoco-test-coverage/pom.xml

@@ -80,7 +80,7 @@
     <dependency>
       <groupId>com.azure</groupId>
       <artifactId>azure-data-appconfiguration</artifactId>
-      <version>1.0.0-beta.8</version> <!-- {x-version-update;com.azure:azure-data-appconfiguration;current} -->
+      <version>1.0.1</version> <!-- {x-version-update;com.azure:azure-data-appconfiguration;current} -->
     </dependency>
     <dependency>
       <groupId>com.azure</groupId>

eng/spotbugs-aggregate-report/pom.xml

@@ -155,7 +155,7 @@
         <dependency>
           <groupId>com.azure</groupId>
           <artifactId>azure-data-appconfiguration</artifactId>
-          <version>1.0.0-beta.8</version> <!-- {x-version-update;com.azure:azure-data-appconfiguration;current} -->
+          <version>1.0.1</version> <!-- {x-version-update;com.azure:azure-data-appconfiguration;current} -->
         </dependency>
         <dependency>
           <groupId>com.azure</groupId>

eng/versioning/version_client.txt

@@ -13,7 +13,7 @@ com.azure:azure-core-management;1.0.0-beta.8;1.0.0-beta.8
 com.azure:azure-core-test;1.1.0-beta.2;1.1.0
 com.azure:azure-core-tracing-opencensus;1.0.0-beta.5;1.0.0-beta.6
 com.azure:azure-core-tracing-opentelemetry;1.0.0-beta.1;1.0.0-beta.2
-com.azure:azure-data-appconfiguration;1.0.0-beta.7;1.0.0-beta.8
+com.azure:azure-data-appconfiguration;1.0.0-beta.7;1.0.1
 com.azure:azure-e2e;1.0.0-beta.1;1.0.0-beta.1
 com.azure:azure-identity;1.0.1;1.1.0-beta.1
 com.azure:azure-messaging-eventhubs;5.0.0-beta.6;5.0.1

sdk/appconfiguration/azure-data-appconfiguration/README.md

@@ -23,7 +23,7 @@ Use the client library for App Configuration to create and manage application co
 <dependency>
     <groupId>com.azure</groupId>
     <artifactId>azure-data-appconfiguration</artifactId>
-    <version>1.0.0-beta.8</version>
+    <version>1.0.1</version>
 </dependency>
 ```
 [//]: # ({x-version-update-end})
@@ -52,7 +52,7 @@ Netty and include OkHTTP client in your pom.xml.
 <dependency>
     <groupId>com.azure</groupId>
     <artifactId>azure-data-appconfiguration</artifactId>
-    <version>1.0.0-beta.8</version>
+    <version>1.0.1</version>
     <exclusions>
       <exclusion>
         <groupId>com.azure</groupId>

sdk/appconfiguration/azure-data-appconfiguration/pom.xml

@@ -13,7 +13,7 @@
 
   <groupId>com.azure</groupId>
   <artifactId>azure-data-appconfiguration</artifactId>
-  <version>1.0.0-beta.8</version> <!-- {x-version-update;com.azure:azure-data-appconfiguration;current} -->
+  <version>1.0.1</version> <!-- {x-version-update;com.azure:azure-data-appconfiguration;current} -->
 
   <name>Microsoft Azure client library for App Configuration</name>
   <description>This package contains the Microsoft Azure App Configuration client library.</description>

sdk/appconfiguration/azure-data-appconfiguration/src/samples/README.md

@@ -20,7 +20,7 @@ Maven dependency for Azure app configuration Client library. Add it to your proj
 <dependency>
     <groupId>com.azure</groupId>
     <artifactId>azure-data-appconfiguration</artifactId>
-    <version>1.0.0-beta.8</version>
+    <version>1.0.1</version>
 </dependency>
 ```
 [//]: # ({x-version-update-end})

sdk/core/azure-core-tracing-opentelemetry/src/samples/CreateConfigurationSettingTracingSample.md

@@ -23,7 +23,7 @@ Sample uses **[opentelemetry-sdk][opentelemetry_sdk]** as implementation package
 <dependency>
     <groupId>com.azure</groupId>
     <artifactId>azure-data-appconfiguration</artifactId>
-    <version>1.0.0-beta.8</version>
+    <version>1.0.1</version>
 </dependency>
 ```
 [//]: # ({x-version-update-end})