Fix WoltNavigationToolbar leading constraint

[TahaTesser]

Fixes leadingNavBarWidget uses more vertical space than trailingNavBarWidget

Code Sample

expand to view the code sample

import 'package:flutter/material.dart';
import 'package:wolt_modal_sheet/wolt_modal_sheet.dart';

void main() {
  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({super.key});

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      home: Builder(builder: (context) {
        return Scaffold(
          body: Center(
            child: TextButton(
              child: const Text('Open WoltModalSheet'),
              onPressed: () {
                WoltModalSheet.show(
                  context: context,
                  pageListBuilder: (context) => [
                    WoltModalSheetPage(
                      isTopBarLayerAlwaysVisible: true,
                      topBarTitle: const Text('Title'),
                      leadingNavBarWidget: Container(
                        color: Colors.blue,
                        child: const Icon(Icons.chevron_left),
                      ),
                      trailingNavBarWidget: Container(
                        color: Colors.red,
                        child: const Icon(Icons.chevron_right),
                      ),
                      child: const Padding(
                        padding: EdgeInsets.all(8.0),
                        child: Center(child: Text('Child')),
                      ),
                    ),
                  ],
                );
              },
            ),
          ), // This trailing comma makes auto-formatting nicer for build methods.
        );
      }),
    );
  }
}

Before

After

Leading Button Splash Constraint (Before)

Leading Button Splash Constraint (After)

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
• My PR includes tests for all changed/updated/fixed behaviors.
• All existing and new tests are passing.
• I updated/added relevant documentation (doc comments with ///).
• The analyzer (melos run analyze) does not report any problems on my PR.
• The package compiles with the minimum Flutter version stated in the pubspec.yaml

Breaking Change

Does your PR require plugin users to manually update their apps to accommodate your change?

• Yes, this is a breaking change.
• No, this is not a breaking change.