Refactor VPN configuration handling to remove device limit management

- Updated the VPN configuration commands and handlers to eliminate the device limit parameter, simplifying the configuration process.
- Adjusted related API documentation to reflect the removal of device limit management, clarifying that this setting is now handled directly in the 3x-ui by node administrators.
- Enhanced the overall codebase by removing unnecessary device limit references across various components, ensuring a cleaner and more maintainable code structure.

frontend/src/shared/api/schema.gen.ts

@@ -1849,8 +1849,6 @@ export interface components {
             /** Format: uuid */
             inboundId: string;
             label: null | string;
-            /** Format: int32 */
-            deviceLimit: null | number | string;
         };
         CreateRoleCommand: {
             name: string;
@@ -1867,8 +1865,6 @@ export interface components {
         };
         EditConfigBody: {
             label: null | string;
-            /** Format: int32 */
-            deviceLimit: null | number | string;
         };
         GetMyConfigsResult: {
             configs: components["schemas"]["VpnConfigDto"][];
@@ -2071,8 +2067,6 @@ export interface components {
             label: null | string;
             protocol: components["schemas"]["VpnProtocol"];
             location: string;
-            /** Format: int32 */
-            deviceLimit: number | string;
             /** Format: int64 */
             usedUpBytes: number | string;
             /** Format: int64 */

frontend/src/shared/api/types.ts

@@ -51,7 +51,6 @@ export type VpnConfigDto = {
   label: string | null
   protocol: VpnProtocol
   location: string
-  deviceLimit: number
   usedUpBytes: number
   usedDownBytes: number
   expiresAt: string | null